Skip to content

Hostname

puremailing.com

Last fetched

puremailing.com resolves to 173.239.5.6, announced in 173.239.5.0/24 by WEBAIR-INTERNET - Webair Internet Development Company Inc. in IS. puremailing.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 · puremailing.comRouting diversity2.4/10Peering density4.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.5/10canon.whisper.security/host/puremailing.com

Resolution chain

IPv6 resolution

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

Attribution

webair development

DNS_OPERATOR, ORIGIN_AS

WHOIS identity

Registrar
iana:146
Registrant organisation
alwaysdata
Contact emails
support@dropcatch.com, b9f967480c965e9b376c75682239bfad-637562@contact.gandi.net, pw-d5d394e8397d63ea8c31f3aad7f13cdc@privacyguardian.org

Subdomains

Subdomain
mail.puremailing.com
mx7.puremailing.com
reseller.puremailing.com
ssl.puremailing.com
tracker.puremailing.com
website.puremailing.com
wiki.puremailing.com
ww9.puremailing.com
www.puremailing.com

Showing 9 of 10. View all subdomains →

Mail and authentication

Nameservers

  • bradley.ns.cloudflare.com
  • desiree.ns.cloudflare.com
  • ns1.expiereddnsmanager.com
  • ns2.expiereddnsmanager.com
  • puremailing.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

  • mx7.puremailing.com
  • mail.puremailing.com

Threat-feed evidence

History

Related pages

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