Skip to content

Hostname

pureftpd.org

Last fetched

pureftpd.org resolves to 37.59.238.213, announced in 37.59.0.0/16 by OVH - OVH SAS in FR. pureftpd.org 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 · pureftpd.orgRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/pureftpd.org

Resolution chain

IPv6 resolution

No AAAA record for pureftpd.org is recorded in WhisperGraph.

Attribution

ovh

ORIGIN_AS

WHOIS identity

Registrar
iana:433
Registrant organisation
fd
Contact emails
09f0c862f98f46094b1b4deb52e777f9bf2b1fc0@whois.gkg.net, 46073761f1835df7896f26ddcb7ae009c01fab0d@whois.gkg.net, ac73139198cefe55d0c35994c23c59ec57bf3609@whois.gkg.net, b9f7381e31152ec162a3af25ce7ea7803fc2c52c@whois.gkg.net, d6a94579277ddcf4fc7df761ecfcca9d03bd99f0@whois.gkg.net

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

  • 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
  • free.ns.c9x.org
  • recital.ns.c9x.org

MX records

  • premiere.mx.c9x.org

SPF policy

  • ip: 37.59.238.212/30
  • ip: 137.74.223.232/30
  • a: pureftpd.org
  • mx: pureftpd.org
  • ip: 164.132.13.235
  • ip: 188.165.248.100
  • ip: 82.64.197.71
  • ip: 82.66.97.28
  • ip: 87.98.134.126
  • ip: 92.222.49.126

Threat-feed evidence

History

Related pages

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