Skip to content

Hostname

mon.gov.mk

Last fetched

mon.gov.mk resolves to 95.180.140.116, announced in 95.180.128.0/18 by NEOTEL-AS-MK - NEOTEL-AS-MK in MK. mon.gov.mk 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 · mon.gov.mkRouting diversity1.5/10Peering density7.5/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint5.6/10canon.whisper.security/host/mon.gov.mk

Resolution chain

IPv6 resolution

No AAAA record for mon.gov.mk is recorded in WhisperGraph.

Attribution

neotel ad skopje

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for mon.gov.mk. 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

Subdomain
1000knigi.mon.gov.mk
admin.mon.gov.mk
anketi-admin.mon.gov.mk
anketi.mon.gov.mk
bi.mon.gov.mk
bipo.mon.gov.mk
dbimport.mon.gov.mk
dbmapper.mon.gov.mk
digit.mon.gov.mk
digitalizirajse.mon.gov.mk
digitalniucebnici.mon.gov.mk
digjitalizohu.mon.gov.mk

Showing 12 of 59. 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

  • ns1.io.mk
  • ns2.io.mk
  • ns1.finki.ukim.mk
  • ns2.finki.ukim.mk
  • ns3.finki.ukim.mk
  • ns4.finki.ukim.mk

MX records

  • relay.mon.gov.mk

SPF policy

  • include: amazonses.com
  • include: spf.protection.outlook.com
  • mx: mon.gov.mk
  • a: relay.mon.gov.mk
  • ip: 212.110.64.198

Threat-feed evidence

History

Related pages

Pivot from mon.gov.mk 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: "mon.gov.mk"})-[: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.