Skip to content

Hostname

sitedistrict.com

Last fetched

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

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Contact emails
mkopala@gmail.com, 2a7b1e4c-220a-4efa-9b60-a7797f9ebe55@identity-protect.org, 2b000894-93f6-49a1-ad6b-02f7c2a19e08@identity-protect.org, b2d50d72-81ac-4ff8-a904-89ac00885907@identity-protect.org, bd79ab69-1bbb-4931-a47d-32938038c2f4@identity-protect.org, d6a2e600-3864-44bc-ba03-c267a8880785@identity-protect.org, e7955000-ed0a-41d0-b125-825b9799e81a@identity-protect.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

  • ns1.sitedistrict.com
  • ns2.sitedistrict.com
  • ns3.sitedistrict.com
  • ns4.sitedistrict.com

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

SPF policy

  • include: amazonses.com
  • include: _spf.google.com
  • include: mailgun.org

Threat-feed evidence

History

Related pages

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