Skip to content

Hostname

next-em.com.mk

Last fetched

next-em.com.mk resolves to 198.72.126.4, announced in 198.72.96.0/19 by IWEB-AS - Leaseweb Canada Inc. in CA. next-em.com.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 · next-em.com.mkRouting diversity2.4/10Peering density4.3/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint6.3/10canon.whisper.security/host/next-em.com.mk

Resolution chain

IPv6 resolution

No AAAA record for next-em.com.mk is recorded in WhisperGraph.

Attribution

leaseweb canada

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for next-em.com.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
live.next-em.com.mk
mail.next-em.com.mk
ns1.next-em.com.mk
ns2.next-em.com.mk
s1.next-em.com.mk
s3.next-em.com.mk
support.next-em.com.mk
www.next-em.com.mk

Showing 8 of 8 subdomains (8 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

  • ns1.cloudns.net
  • ns2.cloudns.net
  • ns3.cloudns.net
  • ns4.cloudns.net
  • pns1.cloudns.net
  • pns2.cloudns.net
  • pns3.cloudns.net
  • pns4.cloudns.net

MX records

  • next-em.com.mk

SPF policy

  • include: sendersrv.com
  • a: next-em.com.mk
  • mx: next-em.com.mk
  • ip: 198.72.126.3
  • ip: 198.72.126.4

Threat-feed evidence

History

Related pages

Pivot from next-em.com.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: "next-em.com.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.