Skip to content

Hostname

pennvet.com

Last fetched

pennvet.com resolves to 104.20.30.103, announced in 104.20.16.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. pennvet.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 · pennvet.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/pennvet.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:2
Registrant organisation
perfect privacy,
Contact emails
as9wh3k72v9@networksolutionsprivateregistration.com, dm5qm9f3487@networksolutionsprivateregistration.com, f52qh6hx86h@networksolutionsprivateregistration.com, g54xd43v8ea@networksolutionsprivateregistration.com, kn8sv9z63re@networksolutionsprivateregistration.com, mh5cg7hd9jw@networksolutionsprivateregistration.com, sd3sf7xe5rz@networksolutionsprivateregistration.com, w55xb6gz5qm@networksolutionsprivateregistration.com, xc2he22g4am@networksolutionsprivateregistration.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

  • jake.ns.cloudflare.com
  • selah.ns.cloudflare.com

MX records

  • mx0a-007f7901.pphosted.com
  • mx0b-007f7901.pphosted.com

SPF policy

  • ip: 149.72.147.186/32
  • ip: 52.190.40.209/32
  • ip: 167.89.101.239/32
  • include: spf.protection.outlook.com
  • mx: pennvet.com
  • include: _spf.samanage.com
  • include: us-k1.o365.crossware.co.nz
  • ip: 50.120.213.66
  • ip: 50.120.213.69
  • ip: 50.217.182.194
  • ip: 50.217.182.206
  • ip: 67.231.145.142
  • ip: 67.231.153.102

Threat-feed evidence

History

Related pages

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