Skip to content

Hostname

seatsandsofas.de

Last fetched

seatsandsofas.de resolves to 213.206.208.107, announced in 213.206.192.0/18 by Interconnect - ML Consultancy in NL. seatsandsofas.de 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 · seatsandsofas.deRouting diversity1.5/10Peering density6.3/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint3.2/10canon.whisper.security/host/seatsandsofas.de

Resolution chain

IPv6 resolution

Attribution

ml consultancy

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for seatsandsofas.de. 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

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Nameservers

  • ns.seatsandsofas.nl
  • ns2.seatsandsofas.nl

MX records

  • mail.seatsandsofas.de

SPF policy

  • ip: 50.31.205.0/24
  • ip: 104.245.209.192/26
  • ip: 50.31.156.96/27
  • include: spf.brevo.com
  • include: se.spf.provider.nl
  • ip: 139.162.150.110
  • ip: 146.190.232.193
  • ip: 167.172.44.66
  • ip: 185.28.5.136
  • ip: 188.93.148.186
  • ip: 195.8.209.100
  • ip: 2001:4018:8800:3:0:0:0:57
  • ip: 213.206.208.107
  • ip: 2a03:7900:111:0:0:50d1:bab9:3
  • ip: 2a03:7900:111:0:a4fb:16ff:fe69:d48f
  • ip: 2a03:7900:2:0:31:3:104:34
  • ip: 31.3.104.161
  • ip: 31.3.107.70
  • ip: 31.3.110.162
  • ip: 85.214.59.230
  • ip: 87.213.104.145
  • ip: 87.213.104.147
  • ip: 87.213.104.149
  • ip: 87.213.98.178
  • ip: 91.238.176.152

Threat-feed evidence

History

Related pages

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