Skip to content

Hostname

nokut.no

Last fetched

nokut.no resolves to 1 IPv4 address operated by MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation in NO.

Nutrition Label

WHISPER CANON · nokut.noRouting diversity1.5/10Peering density6.7/10MOAS conflict✓ noneThreat-feed listings8.0/10WHOIS transparency10.0/10Resolver footprint4.0/10canon.whisper.security/host/nokut.no

Resolution chain

nokut.no resolves to 1 distinct IPv4 address via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.

IPPrefixASNOperatorCountry
51.120.3.13651.120.0.0/16AS8075MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft CorporationNO

WHOIS identity

Registrar
—
Organization
nasjonalt organ for kvalitet i utdanningen nokut
Contact emails

Subdomains

26 observed subdomains of nokut.no.

Subdomain
adfs-esam-qa.nokut.no
akkreditering.nokut.no
applicant-esam.nokut.no
autodiscover.nokut.no
e.nokut.no
eduroam.nokut.no
epost.nokut.no
extfs-esam.nokut.no
fagakk.nokut.no
faportal.nokut.no
forum.nokut.no
gatekeeper.nokut.no
idp-esam.nokut.no
institution-esam.nokut.no
lyncdiscover.nokut.no
mailsrv.nokut.no
mimir-qa.nokut.no
mimir.nokut.no
noki.nokut.no
portal-esam-qa.nokut.no
portal-esam.nokut.no
post.nokut.no
sip.nokut.no
sslvpn.nokut.no
uhportal.nokut.no

Showing 25 of 26. View all subdomains →

Web-graph footprint

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

657 sites link to this hostname.

173 sites linked to from this hostname.

Sample inbound links

Sample outbound links

Threat posture

History

Mail and authentication

MX records

SPF policy

11 SPF mechanisms authorising senders for nokut.no.

MechanismTarget
SPF_Asi-co-smtp01.sysit.net
SPF_Avirusvask.innovasjon.as
SPF_INCLUDE_spf.nanolearning.com
SPF_INCLUDE_spf.uninett.no
SPF_INCLUDEsendgrid.net
SPF_INCLUDEspf.flowmailer.net
SPF_INCLUDEspf.protection.outlook.com
SPF_IP128.0.23.124
SPF_IP128.0.23.74
SPF_IP137.221.26.10
SPF_IP185.7.138.144

Related pages

Pivot deeper into the graph from nokut.no.

Cypher and MCP

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

MATCH (h:HOSTNAME {name: "nokut.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.