Skip to content

Hostname

maid.zone

Last fetched

maid.zone resolves to 194.15.36.203, announced in 194.15.36.0/24 by FlorianKolb - Florian Kolb in DE. maid.zone 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 · maid.zoneRouting diversity1.5/10Peering density3.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.5/10canon.whisper.security/host/maid.zone

Resolution chain

IPv6 resolution

Attribution

florian kolb

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
iana:3862
Registrant organisation
privacy service provided by withheld for privacy ehf
Contact emails
2318229@privacy-link.com

Subdomains

Subdomain
4get.maid.zone
ao.maid.zone
assets.maid.zone
bt.maid.zone
cc.maid.zone
db.maid.zone
delta.maid.zone
dendrite.maid.zone
element.maid.zone
et.maid.zone
fra.maid.zone
fs.maid.zone

Showing 12 of 56. View all 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

Sample outbound links

Mail and authentication

Nameservers

  • 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
  • ns2.chadpug.org
  • ns1.maid.zone
  • ns2.maid.zone
  • ns3.maid.zone
  • ns4.maid.zone

MX records

  • maid.zone

SPF policy

  • mx: maid.zone
  • a: mail.maid.zone
  • ip: 194.15.36.203
  • ip: 2a0b:4e07:bb:0:0:0:0:1
  • ip: 2a0e:97c0:3e3:661:0:0:0:1
  • ip: 2a0e:97c0:3e3:661:0:0:0:2
  • ip: 2a0f:85c1:bac:0:0:0:0:1

Threat-feed evidence

History

Related pages

Pivot from maid.zone 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: "maid.zone"})-[: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.