Skip to content

Hostname

safcodental.com

Last fetched

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

Resolution chain

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

IPv6 resolution

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

WHOIS identity

Registrar
iana:9
Registrant organisation
kenneth saffir
Contact emails
23f8616a0a28fd0a0956ff8a5b8bc384@domaindiscreet.com, 4b207bf50a28fd0a54d35d41a47cc7c9@domaindiscreet.com, 4f5eace30a1612332029bd17f4cf3d7c@domaindiscreet.com, 6c0add870a28fd0a5d48a43cbb650b56@domaindiscreet.com, 80f3e8cc0a28fd0a668ade35ed281226@domaindiscreet.com, b0ctd7139ojs4br6m390p4nhpi@domaindiscreet.com, ct3w86pq9ky@myprivatename.com, gfredrickson@safcodental.com

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-486.awsdns-60.com
  • ns-610.awsdns-12.net
  • ns-1313.awsdns-36.org
  • ns-1856.awsdns-40.co.uk

MX records

  • us-smtp-inbound-1.mimecast.com
  • us-smtp-inbound-2.mimecast.com

SPF policy

  • include: amazonses.com
  • include: emailus.freshservice.com
  • include: us._netblocks.mimecast.com
  • include: spf.protection.outlook.com
  • a: safcodental.com
  • mx: safcodental.com
  • include: em7689.safcodental.com
  • include: 21944014.spf10.hubspotemail.net

Threat-feed evidence

History

Related pages

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