Hostname
picard.de
Last fetched
picard.de resolves to 185.243.135.88, announced in 185.243.132.0/22 by MITTWALD-AS - Robert Meyer trading as "Mittwald CM Service GmbH & Co. KG" in DE. picard.de is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
IPv6 resolution
No AAAA record for picard.de is recorded in WhisperGraph.
Attribution
robert meyer trading mittwald cm
ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for picard.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.
Sample inbound links
Mail and authentication
Nameservers
- alas.geneos.de
- atlas.geneos.de
- gaia.geneos.de
- ns1.geneos.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
MX records
- mx-01-eu-central-1.prod.hydra.sophos.com
- mx-02-eu-central-1.prod.hydra.sophos.com
- gateway.picard.de
- gateway2.picard.de
SPF policy
- ip: 185.98.184.0/24
- ip: 185.98.186.0/24
- ip: 80.82.206.0/26
- ip: 85.214.35.93/32
- include: spf.protection.outlook.com
- a: picard.de
- mx: picard.de
- a: gateway.picard.de
- a: mail.picard.de
- a: mail1.picard.de
- a: mail2.picard.de
- a: nagios.picard.de
- a: ncc-1701.picard.de
- a: pop3.picard.de
- ip: 144.76.106.215
- ip: 212.23.147.218
- ip: 81.169.247.38
- ip: 85.214.255.26
Threat-feed evidence
History
Related pages
Pivot from picard.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: "picard.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.