Hostname
zamlr.com
Last fetched
zamlr.com resolves to 185.62.136.39, announced in 185.62.136.0/22 by WHG-FRA - WHG Hosting Services Ltd in IS. zamlr.com 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
- 185.62.136.39
185.62.136.0/22 · WHG-FRA - WHG Hosting Services Ltd · Reykjavik, IS
IPv6 resolution
No AAAA record for zamlr.com is recorded in WhisperGraph.
Attribution
whg
ORIGIN_AS
WHOIS identity
- Registrar
- iana:48
- Registrant organisation
- whois agent
- Contact emails
- bvtjxcjyd@whoisprivacyprotect.com, nxyfpvdrhl@whoisprivacyprotect.com, rxtbqydhr@whoisprivacyprotect.com
Subdomains
| Subdomain |
|---|
| fa.zamlr.com |
| jr.zamlr.com |
| movie.zamlr.com |
| prod.zamlr.com |
| server.zamlr.com |
| signup.zamlr.com |
| test.zamlr.com |
| www-test.zamlr.com |
| www.zamlr.com |
Showing 9 of 9 subdomains (9 per page).
Mail and authentication
Nameservers
- dns1.name-services.com
- dns2.name-services.com
- dns3.name-services.com
- dns4.name-services.com
- dns5.name-services.com
- 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.zamlr.com.cust.a.hostedemail.com
SPF policy
- include: emde01oc.mail2world.com
- a: emde01oc.mail2world.com
- include: _spf.emfwd.name-services.com
- include: unbouncepages.com
- a: unbouncepages.com
- a: zamlr.com
- mx: zamlr.com
- include: movie.zamlr.com
- a: movie.zamlr.com
- include: prod.zamlr.com
- a: prod.zamlr.com
- include: server.zamlr.com
- a: server.zamlr.com
- include: test.zamlr.com
- a: test.zamlr.com
- ip: 103.72.79.254
- ip: 185.62.136.39
Threat-feed evidence
History
Related pages
Pivot from zamlr.com 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: "zamlr.com"})-[: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.