Skip to content

Hostname

vdata.my

Last fetched

vdata.my resolves to 103.253.14.91, announced in 103.253.14.0/24 by GIGABIT-MY - Gigabit Hosting Sdn Bhd in MY. vdata.my 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 · vdata.myRouting diversity1.5/10Peering density8.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.0/10canon.whisper.security/host/vdata.my

Resolution chain

IPv6 resolution

No AAAA record for vdata.my is recorded in WhisperGraph.

Attribution

gigabit sdn bhd

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for vdata.my. 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
all-qr.vdata.my
clock.vdata.my
columbiaasia.vdata.my
cpanel.vdata.my
cpcalendars.vdata.my
cpcontacts.vdata.my
kerja.vdata.my
library.vdata.my
lms.vdata.my
mail.vdata.my
qr.vdata.my
support.vdata.my

Showing 12 of 26. View all subdomains →

Mail and authentication

Nameservers

  • henrik.ns.cloudflare.com
  • meilani.ns.cloudflare.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

  • mail.vdata.my

SPF policy

  • a: vdata.my
  • mx: vdata.my
  • ip: 124.217.236.30

Threat-feed evidence

History

Related pages

Pivot from vdata.my 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: "vdata.my"})-[: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.