Skip to content

Hostname

gantic.no

Last fetched

gantic.no resolves to 104.26.10.170, announced in 104.26.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. gantic.no 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 · gantic.noRouting diversity2.4/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint5.2/10canon.whisper.security/host/gantic.no

Resolution chain

IPv6 resolution

Attribution

domeneshop

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for gantic.no. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Subdomains

Subdomain
arkiv.gantic.no
blogg.gantic.no
brukt.gantic.no
butikk.gantic.no
deleweb-test.gantic.no
deleweb.gantic.no
demo.gantic.no
ettermarked.gantic.no
fallsikring.gantic.no
intranett.gantic.no
kurs.gantic.no
kursreg.gantic.no

Showing 12 of 20. 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

Sample outbound links

Mail and authentication

Nameservers

  • leah.ns.cloudflare.com
  • ned.ns.cloudflare.com
  • ns1.hyp.net
  • ns2.hyp.net
  • ns3.hyp.net

MX records

  • gantic-no.mail.protection.outlook.com

SPF policy

  • include: spfcloud.letsignit.com
  • include: spf.mandrillapp.com
  • include: spf.protection.outlook.com
  • ip: 167.89.59.11
  • ip: 77.241.105.74

Threat-feed evidence

History

Related pages

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