Hostname
directferries.pl
Last fetched
directferries.pl resolves to 13.33.252.126, announced in 13.33.248.0/21 by AMAZON-02 - Amazon.com, Inc. in US. directferries.pl is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 13.33.252.126
13.33.248.0/21 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 13.33.252.15
13.33.248.0/21 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 13.33.252.71
13.33.248.0/21 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 13.33.252.83
13.33.248.0/21 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 3.166.96.102
3.166.96.0/21 · AMAZON-02 - Amazon.com, Inc. · Kansas City, US
- 3.166.96.26
3.166.96.0/21 · AMAZON-02 - Amazon.com, Inc. · Kansas City, US
- 3.166.96.48
3.166.96.0/21 · AMAZON-02 - Amazon.com, Inc. · Kansas City, US
- 3.166.96.91
3.166.96.0/21 · AMAZON-02 - Amazon.com, Inc. · Kansas City, US
IPv6 resolution
No AAAA record for directferries.pl is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- registrar:az.pl sp. z o.o.
- Registrant organisation
- direct ferries
Subdomains
Showing 2 of 2 subdomains (2 per page).
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Sample inbound links
Mail and authentication
Nameservers
- blue.foundationdns.com
- blue.foundationdns.net
- a.root-servers.net
- b.root-servers.net
- c.root-servers.net
- d.root-servers.net
- e.root-servers.net
- f.root-servers.net
- g.root-servers.net
- h.root-servers.net
- i.root-servers.net
- j.root-servers.net
- k.root-servers.net
- l.root-servers.net
- m.root-servers.net
- blue.foundationdns.org
Threat-feed evidence
History
Related pages
Pivot from directferries.pl into the addresses, networks and registries it depends on.
Cypher and MCP
Reproduce this hostname's resolution chain against graph.whisper.security:
MATCH (h:HOSTNAME {name: "directferries.pl"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.