Skip to content

Hostname

megaloman.com

Last fetched

megaloman.com resolves to 213.81.195.144, announced in 213.81.128.0/17 by SK-TELEKOM - Slovak Telekom, a.s. in SK. megaloman.com 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 · megaloman.comRouting diversity1.5/10Peering density8.3/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.6/10canon.whisper.security/host/megaloman.com

Resolution chain

IPv6 resolution

No AAAA record for megaloman.com is recorded in WhisperGraph.

Attribution

slovak telekom

ORIGIN_AS

WHOIS identity

Registrar
iana:69
Registrant organisation
jan miklasik
Contact emails
miklasik@megaloman.com

Subdomains

Subdomain
interface.megaloman.com
lighthouse.megaloman.com
www.megaloman.com

Showing 3 of 3 subdomains (3 per page).

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
  • ns.ew.sk
  • ns1.ew.sk
  • ns2.ew.sk
  • ns1.swan.sk
  • ns2.swan.sk
  • ns3.swan.sk

MX records

  • megaloman-com.mail.protection.outlook.com

SPF policy

  • include: spf.protection.outlook.com

Threat-feed evidence

History

Related pages

Pivot from megaloman.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: "megaloman.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 20

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