Skip to content

Hostname

samtrygg.se

Last fetched

samtrygg.se resolves to 13.48.18.52, announced in 13.48.0.0/15 by AMAZON-02 - Amazon.com, Inc. in SE. samtrygg.se 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 · samtrygg.seRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.3/10canon.whisper.security/host/samtrygg.se

Resolution chain

IPv6 resolution

No AAAA record for samtrygg.se is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
registrar:loopia ab

Subdomains

Subdomain
almedalen.samtrygg.se
api.samtrygg.se
c02.samtrygg.se
content.samtrygg.se
dev.samtrygg.se
fastighetsagare.samtrygg.se
kundtjanst.samtrygg.se
localcomputer.samtrygg.se
on.samtrygg.se
prod.samtrygg.se
s.samtrygg.se
support.samtrygg.se

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

  • ns-225.awsdns-28.com
  • ns-985.awsdns-59.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-1472.awsdns-56.org
  • ns-1619.awsdns-10.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com

SPF policy

  • include: _spf.google.com
  • include: helpscoutemail.com
  • include: servers.mcsv.net

Threat-feed evidence

History

Related pages

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