Help
RSS
API
Feed
Maltego
Contact
Domain > as1213.heanet.ie
×
Welcome!
Right click nodes and scroll the mouse to navigate the graph.
×
More information on this domain is in
AlienVault OTX
Is this malicious?
Yes
No
DNS Resolutions
Date
IP Address
2025-01-26
193.1.204.215
(
ClassC
)
Port 80
HTTP/1.1 301 Moved PermanentlyServer: nginxDate: Wed, 15 May 2024 22:59:47 GMTContent-Type: text/htmlContent-Length: 162Connection: keep-aliveLocation: https://as1213.heanet.ie/ html>head>title>301 Moved Permanently/title>/head>body>center>h1>301 Moved Permanently/h1>/center>hr>center>nginx/center>/body>/html>
Port 443
HTTP/1.1 200 OKServer: nginxDate: Wed, 15 May 2024 22:59:48 GMTContent-Type: text/htmlContent-Length: 4767Last-Modified: Mon, 16 May 2022 16:19:45 GMTConnection: keep-aliveETag: 628279a1-129fX-Powered html>head> title> HEAnet (AS 1213) Public Peering Policy /title> /head>body>img srcimages/HEAnet%20Logo%202011%20%28blue_text-white_back%29%20Small.png alignleft>br>br>h2> HEAnet Public Peering Policy /h2>br>hr>h3>u>Introduction/u>/h3>strong>HEAnet/strong> (AS 1213) maintains an open public peering policy and will generally entertain peering requests from any organisation at public exchanges points where we have a presence.br>We currently support IPv4 unicast & multicast and IPv6 unicast. We are more than happy to work with IPv6 newcomers and provide any assistance we can.br>br>Private peering requests are also considered, however we operate a more selective private peering policy and in all cases prefer public peering at an open peering exchange.br>br>h3>u>Peering Requirements and Acceptable Usage/u>/h3>The following u>requirements/u> apply to public peering relationships with strong>HEAnet/strong> and complement the requirements of the IXPs at specific peering points.br>Private peers are subject to additional requirement, to be agreed by both parties.ul>li>Both strong>HEAnet/strong> and a prospective peer agree to allow their members and customers to exchange traffic via the public exchange point.li>There will be no charge (zero settlement) for either traffic exchanged or traffic content.li>Each peer will undertake the cost of connecting its own network to the public exchange point.li>Routing information is exchanged with peers via the Border Gateway Protocol version 4 only. Peers may not, without prior explicit written (email) permission, statically route to strong>HEAnet/strong>, or alter next hops such that they are routing to strong>HEAnet/strong> for networks which are not being advertised across the peering sessionli>Traffic exchange is not permitted for networks that are not customers of either peer, except with the explicit written (email) agreement between parties. li>Peers should monitor common traffic and must maintain sufficient bandwidth to the exchange points.li>Each network will, to the best of
View on OTX
|
View on ThreatMiner
Please enable JavaScript to view the
comments powered by Disqus.
Data with thanks to
AlienVault OTX
,
VirusTotal
,
Malwr
and
others
. [
Sitemap
]