Skip to content

Hostname

vapeshopsky.com

Last fetched

vapeshopsky.com resolves to 115.187.18.85, announced in 115.187.18.0/24 by EHL-AS-AP - EBN HOST LIMITED in BD. vapeshopsky.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 · vapeshopsky.comRouting diversity1.5/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/vapeshopsky.com

Resolution chain

IPv6 resolution

Attribution

ebn

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
iana:1479
Registrant organisation
domain administrator
Contact emails
pw-2de58855539b1dd3db2b018e185bf4f2@privacyguardian.org, pw-da7cf56a6b3c0b233c0a9ece94a83b96@privacyguardian.org, pw-f9d198ab918867e9e92c5500583d9170@privacyguardian.org

Subdomains

Subdomain
autodiscover.vapeshopsky.com
cpanel.vapeshopsky.com
cpcontacts.vapeshopsky.com
mail.vapeshopsky.com
webdisk.vapeshopsky.com
webmail.vapeshopsky.com
www.vapeshopsky.com

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

Mail and authentication

Nameservers

  • ns23.ebndns.com
  • ns24.ebndns.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

  • vapeshopsky.com

SPF policy

  • a: vapeshopsky.com
  • mx: vapeshopsky.com
  • ip: 115.187.18.84

Threat-feed evidence

History

Related pages

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