Skip to content

Hostname

studentum.no

Last fetched

studentum.no resolves to 108.138.7.24, announced in 108.138.0.0/21 by AMAZON-02 - Amazon.com, Inc. in DE. studentum.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 · studentum.noRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/studentum.no

Resolution chain

IPv6 resolution

No AAAA record for studentum.no is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrant organisation
studentum as
Contact emails
domains@studentum.se

Subdomains

Subdomain
comwww.studentum.no
messe.studentum.no
msn.studentum.no
skole.studentum.no
studiestart.studentum.no
wildcard.studentum.no
www.studentum.no

Showing 7 of 10. 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

  • ns-51.awsdns-06.com
  • ns-903.awsdns-48.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
  • ns-1227.awsdns-25.org
  • ns-1918.awsdns-47.co.uk

MX records

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

SPF policy

  • include: amazonses.com
  • include: _spf.google.com
  • include: _spf.mail03-userengage.com
  • include: spf.protection.outlook.com
  • include: 826425.spf08.hubspotemail.net

Threat-feed evidence

History

Related pages

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