Skip to content

Hostname

packerrats.com

Last fetched

packerrats.com resolves to 108.167.165.135, announced in 108.167.164.0/23 by ORACLE-BMC-31898 - Oracle Corporation in US. packerrats.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 · packerrats.comRouting diversity1.5/10Peering density8.3/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/packerrats.com

Resolution chain

IPv6 resolution

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

Attribution

oracle

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
iana:886
Registrant organisation
domain privacy service fbo registrant.
Contact emails
packerrats.com@domainprivacygroup.com

Subdomains

Subdomain
autodiscover.packerrats.com
cpanel.packerrats.com
cpcalendars.packerrats.com
cpcontacts.packerrats.com
mail.packerrats.com
webdisk.packerrats.com
webmail.packerrats.com
www.packerrats.com

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

Mail and authentication

Nameservers

  • cns33.hostgator.com
  • cns34.hostgator.com
  • 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

  • packerrats.com

SPF policy

  • ip: 184.173.239.119/32
  • a: packerrats.com
  • mx: packerrats.com
  • include: websitewelcome.com
  • ip: 216.172.170.101
  • ip: 74.53.81.98

Threat-feed evidence

History

Related pages

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