Dashboard / Government / johor.gov.my

Johor

johor.gov.my

Last checked: 1 month ago

Non-Compliant
MGv6C-1.0
55%
Partial Support
Works on IPv6 Only?
Website Not Ready
DNS Not Ready
Email Not Ready

IPv6 Addresses Detected

2001:df2:eb00:d000::9

IPv4 Addresses Detected

103.102.240.146

Network Information

WHOIS

IPv6 Network

Organization
Office of the State Secretary of Johor
Country
MY
ASN
AS9930 TTNET-MY TIME dotCom Berhad No. 14, Jalan Majistret U126 Hicom Glenmarie Industrial Park 40150 Shah Alam Selangor, Malaysia, MY
Network
2001:df2:eb00::/48

IPv4 Network

Organization
Office of the State Secretary of Johor
Country
MY
ASN
AS9930 TTNET-MY TIME dotCom Berhad No. 14, Jalan Majistret U126 Hicom Glenmarie Industrial Park 40150 Shah Alam Selangor, Malaysia, MY
Network
103.102.240.0/22

Web Services

35%
3/8
AAAA Record

The domain has at least one IPv6 address (AAAA DNS record).

✓ 2001:df2:eb00:d000::9

+1
Globally Routable IPv6

The IPv6 addresses are publicly routable — not link-local, ULA, loopback or documentation ranges.

✓ All addresses are globally routable.

+1
HTTP over IPv6

Website reachable on port 80 when connecting via IPv6.

✗ HTTP is not accessible over IPv6.

0
HTTPS over IPv6

Website reachable on port 443 when connecting via IPv6.

✗ HTTPS is not accessible over IPv6.

0
IPv6-Only Reachability

Website responds when connected exclusively over IPv6, with no IPv4 fallback. Simulates what happens when IPv4 is turned off.

✗ Site is not reachable when limited to IPv6-only.

0
TLS Certificate Valid (IPv6)

The SSL/TLS certificate is valid, not expired, and matches the domain when connected via IPv6.

✗ TLS certificate is invalid, expired, or hostname mismatch over IPv6.

0
Dual-Stack (IPv4 + IPv6)

The domain has both A and AAAA records for backwards compatibility during the IPv6 transition.

✓ Domain has both A and AAAA records.

+1
HTTP/3 (QUIC)

Server advertises HTTP/3 support via the Alt-Svc: h3 header.

✗ No HTTP/3 support detected.

0

DNS & DNSSEC

25%
2/5
NS Has AAAA Record

At least one authoritative nameserver has an IPv6 address (AAAA record).

✓ Nameserver has IPv6 address.

+1
NS Reachable via IPv6

Authoritative nameserver accepts TCP connections on port 53 over IPv6.

✗ No nameserver is reachable over IPv6.

0
NS Answers Queries via IPv6

Nameserver actually resolves DNS queries when asked over IPv6 — not just TCP open, but functionally answering.

✗ Nameserver does not answer queries over IPv6.

0
DNSSEC Validated

Full DNSSEC chain-of-trust validation passes. Prevents DNS cache poisoning and spoofing.

✓ DNSSEC fully validated.

+1
Reverse DNS (PTR)

A PTR record exists in ip6.arpa for the IPv6 address. Important for email delivery and network diagnostics.

✗ No PTR record found.

0
DS Record at Parent

Delegation Signer record exists in the parent zone.

✓ DS record found at parent zone.

RRSIG Valid

RRSIG signatures are present and not expired.

✓ RRSIG signatures are current and valid.

Signing Algorithm

The cryptographic algorithm used for DNSSEC signing.

RSASHA256

Email Services

25%
4/6
MX Record Exists

The domain has at least one MX (Mail Exchange) DNS record pointing to a mail server.

✓ MX record found.

+1
MX Server Has IPv6

The highest-priority MX server resolves to an IPv6 address (AAAA record).

✓ MX server has AAAA record.

+1
SMTP Reachable via IPv6

The MX server accepts SMTP connections (port 25) over IPv6 and responds with a 220 banner.

✗ SMTP is not reachable over IPv6.

0
STARTTLS over IPv6

The MX server supports STARTTLS encryption when connected over IPv6.

✗ STARTTLS not available over IPv6.

0
SPF Record

A TXT record with v=spf1 exists, declaring which servers may send email for this domain.

✓ SPF record found.

+1
DKIM Selector

A DKIM public key is published at a common selector, enabling email signature verification.

DKIM selector found: google._domainkey

DMARC Record

A DMARC policy record exists at _dmarc.<domain>, enabling email authentication reporting.

✓ DMARC record found.

+1

IPv4 Baseline

15%
3/3
A Record

The domain has at least one IPv4 address (A DNS record).

✓ 103.102.240.146

+1
HTTP over IPv4

Website reachable on port 80 when connecting via IPv4.

✓ HTTP (port 80) responds over IPv4 — 2258ms TTFB.

+1
HTTPS over IPv4

Website reachable on port 443 when connecting via IPv4.

✓ HTTPS (port 443) responds over IPv4 — 2247ms TTFB.

+1

DNS Resolution Performance

Comparison of A (IPv4) vs AAAA (IPv6) query times across resolvers and transports. Shows median (p50) of 3 samples.

Resolver Transport A (IPv4) AAAA (IPv6) Delta
System Default 29.26 ms (p95: 33) 8.69 ms (p95: 21.06) -20.6 ms
Google IPv4 27.46 ms (p95: 44.29) 41.65 ms (p95: 42.38) +14.2 ms
Google IPv6 23.94 ms (p95: 26.39) 45.47 ms (p95: 55.31) +21.5 ms
Cloudflare IPv4 21.73 ms (p95: 22.85) 18.02 ms (p95: 22.95) -3.7 ms
Cloudflare IPv6 15.35 ms (p95: 29.61) 40.1 ms (p95: 40.3) +24.8 ms
Verification ID: 1553086a-cbbf-4fef-af7f-b07a1028e519 View Audit Trail

Score History

Check History

Last 13 checks

Date Score Status Triggered By
07 Mar 2026
01:27 UTC
55 % Partial manual
07 Mar 2026
01:12 UTC
55 % Partial manual
06 Mar 2026
19:29 UTC
0 % None manual
06 Mar 2026
19:28 UTC
55 % Partial manual
06 Mar 2026
19:19 UTC
55 % Partial manual
06 Mar 2026
18:00 UTC
55 % Partial manual
06 Mar 2026
17:59 UTC
0 % None manual
06 Mar 2026
17:55 UTC
55 % Partial manual
06 Mar 2026
17:49 UTC
55 % Partial manual
06 Mar 2026
17:31 UTC
0 % None manual
06 Mar 2026
17:30 UTC
0 % None manual
06 Mar 2026
03:27 UTC
55 % Partial manual
04 Mar 2026
03:13 UTC
55 % Partial manual