Skip to content

Hostname

penteledata.net

Last fetched

penteledata.net resolves to 209.50.150.195, announced in 209.50.150.0/24 by AS-PTD - PenTeleData Inc. in US. penteledata.net 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 · penteledata.netRouting diversity1.5/10Peering density6.5/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.6/10canon.whisper.security/host/penteledata.net

Resolution chain

IPv6 resolution

No AAAA record for penteledata.net is recorded in WhisperGraph.

Attribution

penteledata

ORIGIN_AS

WHOIS identity

Registrar
iana:69
Registrant organisation
jeff reinhard
Contact emails
prosales@ptd.net

Subdomains

Subdomain
bizvoice.penteledata.net
golf.penteledata.net
intranet.penteledata.net
portal-web.penteledata.net
voice-next.penteledata.net
voice.penteledata.net
www.penteledata.net

Showing 7 of 7 subdomains (7 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

  • dns1.ptd.net
  • dns2.ptd.net
  • dns3.ptd.net
  • dns4.ptd.net
  • dns5.ptd.net
  • dns6.ptd.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

  • mx.ptd.net

SPF policy

  • ip: 204.186.200.0/24
  • ip: 204.186.204.0/24
  • ip: 204.186.29.0/24
  • ip: 204.186.63.0/24
  • ip: 207.44.96.0/24
  • ip: 204.186.98.0/24
  • ip: 204.186.110.182/32
  • include: ptd.spf.syn-alias.com

Threat-feed evidence

History

Related pages

Pivot from penteledata.net 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: "penteledata.net"})-[: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.