Dashboard / Government / jkr.gov.my
Government /

Jabatan Kerja Raya (JKR)

jkr.gov.my

Last checked: 16 hours ago

Download Report
Non-Compliant
MGv6C-1.0
47%
No IPv6 Support
Works on IPv6 Only?
Website Not Ready
DNS Not Ready
Email Not Ready

IPv4 Addresses Detected

110.159.246.128

Network Information

WHOIS

IPv4 Network

Organization
UNIFI-HOME
Country
MY
ASN
AS4788 TTSSB-MY - TM TECHNOLOGY SERVICES SDN. BHD., MY
Network
110.159.224.0/19

Web Services

35%
0/8
AAAA Record

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

✗ No AAAA record found in DNS.

0
Globally Routable IPv6

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

✗ IPv6 address is not globally routable.

0
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 is IPv6-only or IPv4-only.

0
HTTP/3 (QUIC)

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

✗ No HTTP/3 support detected.

0

DNS & DNSSEC

25%
3/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.

✓ Nameserver is reachable via IPv6 on port 53.

+1
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.

No common DKIM selector found.

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).

✓ 110.159.246.128

+1
HTTP over IPv4

Website reachable on port 80 when connecting via IPv4.

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

+1
HTTPS over IPv4

Website reachable on port 443 when connecting via IPv4.

✓ HTTPS (port 443) responds over IPv4 — 122ms 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 6.9 ms (p95: 7.85) 18.54 ms (p95: 19.77) +11.6 ms
Google IPv4 24.39 ms (p95: 27.1) 29.17 ms (p95: 31.22) +4.8 ms
Google IPv6 42.81 ms (p95: 48.52) 42.4 ms (p95: 43.04) -0.4 ms
Cloudflare IPv4 9.79 ms (p95: 21.25) 9.04 ms (p95: 9.81) -0.8 ms
Cloudflare IPv6 21.5 ms (p95: 59.92) 10.15 ms (p95: 20.38) -11.4 ms
Tamper-evident evidence record

This result is backed by an HMAC-SHA256 signed evidence record. Scan the code or follow the link to verify the audit trail independently.

9f0ac658-4c46-44c9-a815-993ecf46589a
View Audit Trail →

Score History

Check History

Last 7 checks

Date Score Status Triggered By
13 Jun 2026
00:57 UTC 		47 % None scheduled
07 Mar 2026
01:08 UTC 		47 % Partial manual
06 Mar 2026
19:01 UTC 		47 % Partial manual
06 Mar 2026
17:45 UTC 		47 % Partial manual
06 Mar 2026
17:19 UTC 		27 % None manual
06 Mar 2026
11:26 UTC 		32 % Partial manual
04 Mar 2026
03:11 UTC 		32 % Partial manual