Skip to content

Hostname

huddatingapp.com

Last fetched

huddatingapp.com is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. huddatingapp.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 · huddatingapp.comRouting diversity0.0/10Peering density0.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/huddatingapp.com

Resolution chain

No IPv4 resolution is recorded for huddatingapp.com in WhisperGraph.

IPv6 resolution

IPv6 resolution is temporarily unavailable.

The graph did not answer within the page budget. Refresh in a moment to retry — fresh data is fetched on the next visit.

Attribution is temporarily unavailable.

The graph did not answer within the page budget. Refresh in a moment to retry — fresh data is fetched on the next visit.

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of huddatingapp.com owner
Contact emails
1bc0360d-0c17-40a6-b24e-ef850b016508@identity-protect.org, 20d914ac-46f2-4a57-a380-3af5b6fc8860@identity-protect.org, 8f44ec88-fdee-49fd-aea8-ee068a32e8d9@identity-protect.org, 9176f3b8-953d-4081-a863-992260d2c2ec@identity-protect.org, d2e662fb-c48a-413f-8f00-df06d80771f2@identity-protect.org, fecdeb94-abc8-4023-8f1f-30474f7cadae@identity-protect.org, owner-219046@huddatingapp.com.whoisprivacyservice.org

Subdomains

Subdomains is temporarily unavailable.

The graph did not answer within the page budget. Refresh in a moment to retry — fresh data is fetched on the next visit.

Mail and authentication

Nameservers

  • ns-180.awsdns-22.com
  • ns-578.awsdns-08.net
  • ns-1307.awsdns-35.org
  • ns-2020.awsdns-60.co.uk

Threat-feed evidence

History

Related pages

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