Skip to content

Hostname

proxfree.com

Last fetched

proxfree.com resolves to 168.235.81.76, announced in 168.235.80.0/22 by RAMNODE - InMotion Hosting, Inc. in US. proxfree.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 · proxfree.comRouting diversity2.4/10Peering density3.6/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/proxfree.com

Resolution chain

IPv6 resolution

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

Attribution

inmotion

ORIGIN_AS

WHOIS identity

Registrar
iana:1479
Registrant organisation
domain administrator
Contact emails
eea87e4b55bc46a6b1db794d0cd1debe.protect@whoisguard.com, 9609366b1b99ffbd0f336bcc869e9138-1321974@contact.gandi.net, a2e1ed9d3ae5dddae39a78bbb559de34-1321974@contact.gandi.net, pw-166fe5c45b776cd82ea6db79ae4a090d@privacyguardian.org, nick@nitrad.co.uk

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

  • ns1.dneasy.com
  • ns2.dneasy.com
  • ns3.dneasy.com
  • ns4.dneasy.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

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com

SPF policy

  • include: _spf.google.com

Threat-feed evidence

History

Related pages

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