Skip to content

Hostname

hydrantid.com

Last fetched

hydrantid.com resolves to 108.138.51.28, announced in 108.138.48.0/21 by AMAZON-02 - Amazon.com, Inc. in IE. hydrantid.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 · hydrantid.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/hydrantid.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of hydrantid.com owner
Contact emails
hydrantid.com@domainsbyproxy.com, 22849fb8-e847-48f4-b7e0-b0bc03d2418d@identity-protect.org, 3c28480e-d768-4c45-8afa-87b58ae43736@identity-protect.org, 3ffef297-ebd1-4726-8a0e-2d87a8b42bf1@identity-protect.org, 746a27c5-bae2-4bfb-a850-4b12005560f4@identity-protect.org, ab7a414d-ba3a-47a4-8b3d-20b8cf33185d@identity-protect.org, c37621b8-ee58-45bd-8041-b30f31acc54f@identity-protect.org, f6dd48d7-c1f9-4822-be41-f433ed76713e@identity-protect.org, owner-2218808@hydrantid.com.whoisprivacyservice.org, owner-7165866@hydrantid.com.whoisprivacyservice.org, owner-738738@hydrantid.com.whoisprivacyservice.org, owner-8005931@hydrantid.com.whoisprivacyservice.org, owner@hydrantid.com.whoisprivacyservice.org

Subdomains

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Nameservers

  • ns-327.awsdns-40.com
  • ns-536.awsdns-03.net
  • ns-1207.awsdns-22.org
  • ns-1957.awsdns-52.co.uk

MX records

  • hydrantid-com.mail.protection.outlook.com

SPF policy

  • include: spf.protection.outlook.com

Threat-feed evidence

History

Related pages

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