Skip to content

Hostname

tdsc.com

Last fetched

tdsc.com resolves to 13.89.57.7, announced in 13.64.0.0/11 by MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation in US. tdsc.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 · tdsc.comRouting diversity1.5/10Peering density8.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/tdsc.com

Resolution chain

IPv6 resolution

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

Attribution

Azure

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:299
Registrant organisation
california dental association
Contact emails
87460430351296-0f1355@whoisprivacyservices.com.au, netsol.verification@henryschein.com, carolc@cda.org, carol.clinger@cda.org, itinvoices@cda.org, blaine.wasylkiw@cda.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

  • dbru.br.ns.els-gms.att.net
  • dmtu.mt.ns.els-gms.att.net
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net

MX records

  • mxa-001d3a01.gslb.pphosted.com
  • mxb-001d3a01.gslb.pphosted.com

SPF policy

  • ip: 168.245.127.0/24
  • include: spf.protection.outlook.com
  • include: spf-001d3a01.pphosted.com
  • mx: tdsc.com
  • include: _spfrecord1.tdsc.com
  • include: 4822814.spf10.hubspotemail.net

Threat-feed evidence

History

Related pages

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