Skip to content

Hostname

mail.maytap.org

Last fetched

mail.maytap.org resolves to 2 IPv4 addresses operated by AS197450 in TR.

Nutrition Label

WHISPER CANON · mail.maytap.orgRouting diversity2.4/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.6/10canon.whisper.security/host/mail.maytap.org

Resolution chain

mail.maytap.org resolves to 2 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.

IPPrefixASNOperatorCountry
185.113.223.36185.113.223.0/24AS197450—TR
185.9.39.186185.9.39.0/24AS199608—TR

WHOIS identity

No WHOIS records are currently associated with mail.maytap.org in WhisperGraph.

Threat posture

History

Mail and authentication

MX records

SPF policy

10 SPF mechanisms authorising senders for mail.maytap.org.

MechanismTarget
SPF_Amail.maytap.org
SPF_INCLUDEgmail.com
SPF_IP185.113.223.36
SPF_IP185.244.147.243
SPF_IP185.9.39.186
SPF_IP188.132.232.14
SPF_IP212.64.199.210
SPF_IP45.151.2.87
SPF_IP78.135.111.136
SPF_MXmail.maytap.org

Related pages

Pivot deeper into the graph from mail.maytap.org.

Cypher and MCP

Reproduce the resolution chain directly against graph.whisper.security:

MATCH (h:HOSTNAME {name: "mail.maytap.org"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
      -[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.