Skip to content

Hostname

reimageplus.com

Last fetched

reimageplus.com resolves to 172.96.191.154, announced in 172.96.190.0/23 by LEASEWEB-APAC-SIN-11 - LEASEWEB SINGAPORE PTE. LTD. in SG. reimageplus.com is listed by 2 threat feeds; reconciled level HIGH.

Threat posture

40threat score (procedure-native scale)

HIGH

Listed by 2 threat feeds. At least one source recommends blocking.

Threat feeds listing this
2
Verdict coverage
malicious-evidenced
First seen on a feed
Wed, 26 Aug 2026 14:44:38 GMT
Last seen on a feed
Tue, 15 Sep 2026 00:18:34 GMT

Nutrition Label

WHISPER CANON · reimageplus.comRouting diversity3.5/10Peering density3.6/10MOAS conflict✓ noneThreat-feed listings6.8/10WHOIS transparency10.0/10Resolver footprint8.9/10canon.whisper.security/host/reimageplus.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · MAIL_RECEIVER, ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:146
Registrant organisation
******** ********
Contact emails
********@*****.***, reimageplus.com@domainsbyproxy.com, domains@efix.com

Subdomains

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.

Mail and authentication

Nameservers

  • ali.ns.cloudflare.com
  • clyde.ns.cloudflare.com
  • ns43.domaincontrol.com
  • ns44.domaincontrol.com
  • ns65.domaincontrol.com
  • ns66.domaincontrol.com
  • ns5.hawkhost.com
  • ns6.hawkhost.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

  • reimageplus.com
  • _dc-mx.998adaaed278.reimageplus.com

Threat-feed evidence

History

Related pages

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