Skip to content

Hostname

park-control.de

Last fetched

park-control.de resolves to 108.143.51.92, announced in 108.140.0.0/14 by MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation in NL. park-control.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 · park-control.deRouting diversity1.5/10Peering density8.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.0/10canon.whisper.security/host/park-control.de

Resolution chain

IPv6 resolution

No AAAA record for park-control.de is recorded in WhisperGraph.

Attribution

Github

saas · ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for park-control.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
autodiscover.park-control.de
jahrhunderthalle.park-control.de
matomo.park-control.de
scanpay.park-control.de
ticket-api.park-control.de
ticket.park-control.de
www.park-control.de

Showing 7 of 7 subdomains (7 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
  • ns.udag.net
  • ns.udag.org

MX records

  • mx.eu.mailmarshal.cloud

SPF policy

  • ip: 213.221.115.115/32
  • ip: 81.209.149.215/32
  • include: spf.eu.mailmarshal.cloud
  • a: mail03.axsos.de
  • a: mail04.axsos.de
  • a: park-control.de
  • mx: park-control.de
  • include: deliverabilitymanager.net

Threat-feed evidence

History

Related pages

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