Skip to content

Hostname

seedingup.de

Last fetched

seedingup.de resolves to 192.124.249.56, announced in 192.124.249.0/24 by SUCURI-SEC - Sucuri in US. seedingup.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 · seedingup.deRouting diversity2.4/10Peering density3.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.2/10canon.whisper.security/host/seedingup.de

Resolution chain

IPv6 resolution

No AAAA record for seedingup.de is recorded in WhisperGraph.

Attribution

sucuri

ORIGIN_AS

WHOIS identity

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

Subdomain
account.seedingup.de
lp.seedingup.de
typo3.seedingup.de
wp.seedingup.de
wp3.seedingup.de
www.seedingup.de

Showing 6 of 6 subdomains (6 per page).

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.udag.de
  • 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.udag.net
  • ns.udag.org

MX records

  • mxlb.ispgateway.de
  • mxlbpu.ispgateway.de

SPF policy

  • include: ispgateway.de
  • include: spf.kbmpro.de
  • a: seedingup.de
  • mx: seedingup.de
  • include: spf.emailsys.net

Threat-feed evidence

History

Related pages

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