Hostname
block-domains.com
Last fetched
block-domains.com resolves to 18.158.50.5, announced in 18.156.0.0/14 by AMAZON-02 - Amazon.com, Inc. in DE. block-domains.com 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
- 18.158.50.5
18.156.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.122.34.206
- 3.66.21.209
3.64.0.0/12 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 35.156.0.190
35.156.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 63.182.29.179
63.180.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
IPv6 resolution
No AAAA record for block-domains.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:468
- Registrant organisation
- on behalf of block-domains.com owner
- Contact emails
- 187e46ff-fc4d-4434-aa47-e3731c39045f@identity-protect.org, 4360fd45-ec1e-4740-b6bc-9a8a6ab43198@identity-protect.org, 64725f8c-8448-46d0-bf57-eae4f48dc534@identity-protect.org, 7735d36b-f619-4ede-b06a-17b84e7ac630@identity-protect.org, 7cd3db56-c5aa-4d66-8dbe-5eb1653b5f14@identity-protect.org, b9ce5016-0975-4205-95e8-bd77d79a4771@identity-protect.org, ed8c600d-8cc1-413a-9776-c6fba57c4bc9@identity-protect.org, owner-10446670@block-domains.com.whoisprivacyservice.org
Mail and authentication
Nameservers
- ns-383.awsdns-47.com
- ns-653.awsdns-17.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
- ns-1241.awsdns-27.org
- ns-1722.awsdns-23.co.uk
SPF policy
- include: _phishspf.knowbe4.com
Threat-feed evidence
History
Related pages
Pivot from block-domains.com 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: "block-domains.com"})-[: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.