Skip to content

Hostname

tu.no

Last fetched

tu.no resolves to 2 IPv4 addresses operated by REDPILL-LINPRO Redpill Linpro in NO.

Nutrition Label

WHISPER CANON · tu.noRouting diversity—Peering density—MOAS conflict—Threat-feed listings—WHOIS transparency—Resolver footprint—canon.whisper.security/host/tu.no

Resolution chain

tu.no resolves to 2 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.

IPPrefixASNOperatorCountry
87.238.41.5887.238.32.0/19AS39029REDPILL-LINPRO Redpill LinproNO
87.238.41.5987.238.32.0/19AS39029REDPILL-LINPRO Redpill LinproNO

WHOIS identity

WHOIS data is temporarily unavailable. Refresh in a moment to retry.

Subdomains

Subdomain count is temporarily unavailable. Refresh in a moment to retry.

Web-graph footprint

Distinct hostnames that link to or from tu.no in the public web crawl.

Sample inbound links

Sample outbound links

Threat posture

History

Mail and authentication

MX records

SPF policy

7 SPF mechanisms authorising senders for tu.no.

MechanismTarget
SPF_Atu.no
SPF_INCLUDE3307297.spf06.hubspotemail.net
SPF_INCLUDE_spf.google.com
SPF_INCLUDE_spf.tu.c.bitbit.net
SPF_INCLUDEfdspfeuc.freshemail.io
SPF_INCLUDEsendgrid.net
SPF_IP176.58.114.74

Related pages

Pivot deeper into the graph from tu.no.

Cypher and MCP

Reproduce the resolution chain directly against graph.whisper.security:

MATCH (h:HOSTNAME {name: "tu.no"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
      -[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.