Skip to content

Hostname

elink-pm.com

Last fetched

elink-pm.com resolves to 13.248.188.167, announced in 13.248.176.0/20 by AMAZON-02 - Amazon.com, Inc. in CA. elink-pm.com is listed by 1 threat feed; reconciled level HIGH.

Threat posture

40threat score (procedure-native scale)

HIGH

Listed by 1 threat feed. At least one source recommends blocking.

Threat feeds listing this
1
Verdict coverage
malicious-evidenced
First seen on a feed
Wed, 26 Aug 2026 14:49:47 GMT
Last seen on a feed
Tue, 22 Sep 2026 23:26:40 GMT

Nutrition Label

WHISPER CANON · elink-pm.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings8.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/elink-pm.com

Resolution chain

IPv6 resolution

No AAAA record for elink-pm.com is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:460
Registrant organisation
e-link plastic
Contact emails
mark@mail.elink-plastic.com, mark@elink-pm.com

Subdomains

Subdomain
mailfilter.elink-pm.com
www.elink-pm.com

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

  • ns-202.awsdns-25.com
  • ns-573.awsdns-07.net
  • 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-1221.awsdns-24.org
  • ns-1951.awsdns-51.co.uk

MX records

  • mailfilter.elink-pm.com

SPF policy

  • include: spf.163.com
  • include: _spf.ready-market.com
  • include: hibox.hinet.net

Threat-feed evidence

History

Related pages

Pivot from elink-pm.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: "elink-pm.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.