Skip to content

Hostname

vlandvn.com

Last fetched

vlandvn.com resolves to 103.28.36.218, announced in 103.28.36.0/22 by NHANHOA-AS-VN - NhanHoa Software company in VN. vlandvn.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
Sun, 06 Sep 2026 07:37:39 GMT

Nutrition Label

WHISPER CANON · vlandvn.comRouting diversity1.5/10Peering density3.1/10MOAS conflict✓ noneThreat-feed listings8.0/10WHOIS transparency10.0/10Resolver footprint8.5/10canon.whisper.security/host/vlandvn.com

Resolution chain

IPv6 resolution

No AAAA record for vlandvn.com is recorded in WhisperGraph.

Attribution

nhanhoa software

ORIGIN_AS

WHOIS identity

Registrar
iana:1649
Registrant organisation
cong ty co phan dau tu va kinh doanh bat dong san v-land vi
Contact emails
haonva@gmail.com, nsscentral@gmail.com

Subdomains

Subdomain
cpanel.vlandvn.com
cpcalendars.vlandvn.com
cpcontacts.vlandvn.com
hostmaster.vlandvn.com
mail.vlandvn.com
webdisk.vlandvn.com
webmail.vlandvn.com
wildcard.vlandvn.com
www.vlandvn.com

Showing 9 of 9 subdomains (9 per page).

Mail and authentication

Nameservers

  • nsbak.dotvndns.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
  • ns1.dotvndns.vn
  • ns2.dotvndns.vn
  • ns1.pavietnam.vn
  • ns2.pavietnam.vn

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

SPF policy

  • include: _spf.google.com

Threat-feed evidence

History

Related pages

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