Domain Intelligence Report
Gathering intelligence... (11/12)
DNS
WHOIS
Security
Email
DNSSEC
Threats
Deliverability
SSL/TLS
HTTP
Tech Stack
Subdomains
Archive
Safe
DNSSEC unsignedno attacks or spoofing
Up
HTTP 200reachable and responding
Right
Set up Page Watchit is what it is
Ready
36d aheadyou see what's coming
Outline
DNS
1 A · 3 MX · 3 NS · 1 SOA · 7 TXT · 1 AAAA
SSL/TLS
Sectigo Limited · TLSv1.3 · expires in 36d · 2 SANs
Email Auth
SPF ✓ · DKIM ✓ · DMARC ✓ (p=quarantine)
DNSSEC
not signed
Tech Stack
Email: Microsoft 365 · nginx
HTTP
1 redirect → 200 · HSTS ✓ · CSP ✓ · X-Frame ✓ · Nosniff ✗
Security
B (180/215) · 2 high
Threats
risk: none
Deliverability
82% B (82/100 points) · 3 MX · 10 IPs · 7 issue(s)
Subdomains
2 found · 100 answered (12 timed out) — gitlab, pop3
Web Archive
first snapshot 2002-05-26 · 24y archived
DNS Recordschecked 2.7d ago
Details1 A · 3 MX · 3 NS · 1 SOA · 7 TXT · 1 AAAA
WHOIS
Then vs Nownew
No card for this name. We compare then and now for domains that are in the top million and had an AboutUs page. That says nothing about this domain’s age or safety.
Check what it is now →SSL/TLSchecked 2.7d ago
DetailsValid certificate
Issuer: Sectigo Limited
Protocol: TLSv1.3
Expires in 36 days
2 SAN(s)
Securitychecked 2.7d ago
DetailsB
180/215
2 high
Weakest: Basic Security, Record Security
Email Authchecked 2.7d ago
DetailsSPFDKIMDMARC
Policy: quarantine
DNSSECchecked 2.7d ago
DetailsNot DNSSEC-signed
Tech Stackchecked 2.7d ago
DetailsnginxEmail: Microsoft 365Google Search Console
HTTP / Headerschecked 2.7d ago
Details1 redirect(s) → 200
HSTSCSPX-FrameNosniff
Threatschecked 2.7d ago
DetailsRisk: none · score 0
Zone census
Subdomainschecked 2.7d ago
DetailsWeb Archivechecked 2.7d ago
DetailsFirst archived: 2002-05-26
~24 years of history
Archive.org's index did not answer, so the latest date is the newest capture that loaded; a later redirect or error capture may exist.
Deliverabilitychecked 2.7d ago
Details82%B
82/100 points · 7 issue(s)
3 MX · 10 IP(s)
Top fix: MX IP 52.101.137.2 has no PTR (reverse DNS)
IPv6
Measured 2026-11-04 00:05 UTC · aaaa.botF
Publishes an IPv6 address that does not answer.
Connections on 443 and 80 got no answer, and probes on other continents agree.
Probes on other continents could not connect either, so this is not only our view.
- ✗ vianet.com.np: published, no answer (0 of 1)
- ✗ www.vianet.com.np: published, no answer (0 of 1)
- ✗ Mail: 1 of 3 servers have IPv6
- ✓ Nameservers: 3 of 3 have IPv6
Details: published addresses and what answered
| Name | Published address (AAAA) | Answers when we connect |
|---|---|---|
| vianet.com.np | Published2404:7c00:1:400::2 | Answers when we connect✗ no answer on 443 or 80 |
| www.vianet.com.np | Published2404:7c00:1:400::2 | Answers when we connect✗ no answer on 443 or 80 |
Publishedmx-1.vianet.com.npvianet-com-np.mail.protection.outlook.commx-2.vianet.com.np | Answers when we connect✗ no IPv6✓ has IPv6✗ no IPv6 | |
| Nameservers | Publishedanyns.pch.netdns2.vianet.com.npdns1.vianet.com.np | Answers when we connect✓ has IPv6✓ has IPv6✓ has IPv6 |
First measured with IPv6 on 2026-11-04Changes are recorded from here on, each with its date.
Want to know when vianet.com.np changes?
Monitor it free — 5 monitors, uptime checks every 5 minutes, email alerts when something breaks. No card required.