Skip to content

Hostname

compliancephd.com

Last fetched

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

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:9
Registrant organisation
perfect privacy,
Contact emails
0fa5b9970a28fd0a672559e92f7637de@domaindiscreet.com, 4ff43da30a28fd0a21aaf2b009742f9c@domaindiscreet.com, 57964360@myprivatename.com, 6dad96f30a28fd0a2b81c48249beb263@domaindiscreet.com

Subdomains

Subdomain
blog.compliancephd.com
www.compliancephd.com

Showing 2 of 2 subdomains (2 per page).

Web-graph footprint

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

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • ns-392.awsdns-49.com
  • ns-783.awsdns-33.net
  • ns-1044.awsdns-02.org
  • ns-1664.awsdns-16.co.uk

MX records

  • mx001.register.xion.oxcs.net
  • mx002.register.xion.oxcs.net
  • mx003.register.xion.oxcs.net
  • mx004.register.xion.oxcs.net

SPF policy

  • ip: 108.178.13.210/29
  • include: spf.cloudus.oxcs.net
  • ip: 108.178.13.211
  • ip: 108.178.13.212
  • ip: 108.178.13.213
  • ip: 108.178.13.214

Threat-feed evidence

History

Related pages

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