Skip to content

Hostname

comment2434.com

Last fetched

comment2434.com resolves to 13.226.244.122, announced in 13.226.244.0/22 by AMAZON-02 - Amazon.com, Inc. in DE. comment2434.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · comment2434.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/comment2434.com

Resolution chain

IPv6 resolution

No AAAA record for comment2434.com is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of comment2434.com owner
Contact emails
0928a0de-c13d-4dd2-bb4d-e94f22ec0f59@identity-protect.org, 0d40ef10-a769-4f74-b539-3900f1ba909f@identity-protect.org, 43d80dab-ed40-4cf9-8c78-44f16713cdf2@identity-protect.org, 81a18aa7-3c0a-462b-a235-b1db4d7cdb7f@identity-protect.org, 97630c9b-eeb0-40bd-8973-cc5fc283cfab@identity-protect.org, d1989efd-36ed-49cd-8e0d-0073b8d6b02e@identity-protect.org, e759e775-670a-40fd-be6a-a5a9d5399812@identity-protect.org, owner-2354260@comment2434.com.whoisprivacyservice.org

Subdomains

Subdomain
vtuber.comment2434.com

Showing 1 of 2. View all subdomains →

Mail and authentication

Nameservers

  • ns-487.awsdns-60.com
  • ns-565.awsdns-06.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-1249.awsdns-28.org
  • ns-1746.awsdns-26.co.uk

Threat-feed evidence

History

Related pages

Pivot from comment2434.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: "comment2434.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 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.