Hostname
mandmdirect.de
Last fetched
mandmdirect.de resolves to 104.81.5.164, announced in 104.81.0.0/20 by AKAMAI-AS - Akamai Technologies, Inc. in DE. mandmdirect.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
- 104.81.5.164
104.81.0.0/20 · AKAMAI-AS - Akamai Technologies, Inc. · Berlin, DE
- 2.16.33.163
2.16.32.0/23 · AKAMAI-AS - Akamai Technologies, Inc. · Frankfurt am Main, DE
- 23.210.118.158
23.210.112.0/20 · AKAMAI-AS - Akamai Technologies, Inc. · Frankfurt am Main, DE
- 23.223.220.217
23.223.220.0/22 · AKAMAI-AS - Akamai Technologies, Inc. · Seattle, US
- 23.45.104.212
23.45.96.0/20 · AKAMAI-AS - Akamai Technologies, Inc. · Frankfurt am Main, DE
- 23.56.207.79
23.56.200.0/21 · AKAMAI-AS - Akamai Technologies, Inc. · Frankfurt am Main, DE
- 23.58.13.162
23.58.12.0/22 · AKAMAI-AS - Akamai Technologies, Inc. · Kolkata, IN
IPv6 resolution
No AAAA record for mandmdirect.de is recorded in WhisperGraph.
Attribution
akamai
ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for mandmdirect.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
- a1-30.akam.net
- a13-65.akam.net
- a20-66.akam.net
- a22-67.akam.net
- a26-64.akam.net
- a3-65.akam.net
MX records
- mxa-002bfb01.gslb.pphosted.com
- mxb-002bfb01.gslb.pphosted.com
SPF policy
- include: spf-002bfb01.pphosted.com
- include: mail.zendesk.com
Threat-feed evidence
History
Related pages
Pivot from mandmdirect.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: "mandmdirect.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.