Skip to content

Hostname

nofrag.com

Last fetched

nofrag.com resolves to 109.234.167.89, announced in 109.234.164.0/22 by O2SWITCH - O2SWITCH SAS in FR. nofrag.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 · nofrag.comRouting diversity1.5/10Peering density3.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/nofrag.com

Resolution chain

IPv6 resolution

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

Attribution

o2switch

ORIGIN_AS

WHOIS identity

Registrar
iana:74
Registrant organisation
nicolas roux
Contact emails
030a91dd233a2d3cde2b518b52133a78-ns643@contact.gandi.net, 3dc633abfaf0feaab203be3ea3152d1e-336154@contact.gandi.net, 8bcf491e58291c55d97b7c70568e72ca-336154@contact.gandi.net, bf8a75311bf4355443463184d4c3b022-336154@contact.gandi.net

Subdomains

Subdomain
ava.nofrag.com
forum.nofrag.com
mail.nofrag.com
pix.nofrag.com
q3lfr.nofrag.com
s3.nofrag.com
static.nofrag.com
test.nofrag.com
wiki.nofrag.com
www.nofrag.com

Showing 10 of 12. View all subdomains →

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

  • ns1.o2switch.net
  • ns2.o2switch.net
  • 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

  • mail.nofrag.com

SPF policy

  • a: nofrag.com
  • mx: nofrag.com
  • include: spf.jabatus.fr
  • ip: 109.234.167.89

Threat-feed evidence

History

Related pages

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