Domain report: mobilevikings.be

Registration

info

.be country-code

Found

TLD: .be (country-code)
ICANN policies apply: no

Checks

i

.be is a country-code TLD (ccTLD)

Country-code TLD: governed by its local registry under national policy, not by an ICANN contract. Registrar accreditation, dispute resolution and RDAP/WHOIS rules are set by the registry.

#1
✓ TLD delegated and signed #2

.be is delegated in the root zone and DNSSEC-signed.
i

Registration data not available

No registration data via RDAP: the registry of .be offers no RDAP service. Many ccTLD registries don't offer RDAP; check the registry's WHOIS instead.

#3

Delegation

warn

ns-1508.awsdns-60.org, ns-1761.awsdns-28.co.uk, ns-758.awsdns-30.net

Found

Parent zone: be
Delegation from: a.nsset.be (194.0.6.1)
NS at the parent: ns-1508.awsdns-60.org, ns-1761.awsdns-28.co.uk, ns-758.awsdns-30.net
NS in the zone: ns-1508.awsdns-60.org, ns-1761.awsdns-28.co.uk, ns-50.awsdns-06.com, ns-758.awsdns-30.net

Nameserver	Addresses	Network (AS)	Glue
ns-1508.awsdns-60.org	205.251.197.228 2600:9000:5305:e400::1	AS16509 AMAZON-02 - Amazon.com, Inc., US AS16509 AMAZON-02 - Amazon.com, Inc., US	-
ns-1761.awsdns-28.co.uk	205.251.198.225 2600:9000:5306:e100::1	AS16509 AMAZON-02 - Amazon.com, Inc., US AS16509 AMAZON-02 - Amazon.com, Inc., US	-
ns-50.awsdns-06.com (zone only)	205.251.192.50 2600:9000:5300:3200::1	AS16509 AMAZON-02 - Amazon.com, Inc., US AS16509 AMAZON-02 - Amazon.com, Inc., US	-
ns-758.awsdns-30.net	205.251.194.246 2600:9000:5302:f600::1	AS16509 AMAZON-02 - Amazon.com, Inc., US AS16509 AMAZON-02 - Amazon.com, Inc., US	-

Checks

✓ 3 nameservers #6

Delegated to ns-1508.awsdns-60.org, ns-1761.awsdns-28.co.uk, ns-758.awsdns-30.net.
!

NS sets differ

The nameservers at the parent and in the zone should be the same. Only in the zone: ns-50.awsdns-06.com. ns-1508.awsdns-60.org, ns-1761.awsdns-28.co.uk, ns-50.awsdns-06.com, ns-758.awsdns-30.net report NS ns-1508.awsdns-60.org ns-1761.awsdns-28.co.uk ns-50.awsdns-06.com ns-758.awsdns-30.net.

#7
✓ No glue needed #8

All nameservers are outside the zone, so no glue records are needed.
✓ All names resolve #9

Every nameserver name has an address and is not an alias.
✓ Nameservers in different networks #10

The nameservers are spread over 4 IPv4 /24s and 4 IPv6 /48s.
i

All nameservers in one AS

All nameserver addresses are announced by one network operator (AS16509 (AMAZON-02 - Amazon.com, Inc., US): 8 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.

#11
✓ Nameserver names under 3 TLDs #12

Nameserver names use the TLDs .net, .org, .uk.
✓ All reachable over IPv6 #13

Every nameserver has an IPv6 address.

Nameservers

pass

8 of 8 addresses answer authoritatively

Found

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
ns-1508.awsdns-60.org 205.251.197.228	NOERROR, 3 ms, authoritative	no	yes / yes	refused	-
ns-1508.awsdns-60.org 2600:9000:5305:e400::1	NOERROR, 4 ms, authoritative	no	yes / yes	refused	-
ns-1761.awsdns-28.co.uk 205.251.198.225	NOERROR, 9 ms, authoritative	no	yes / yes	refused	-
ns-1761.awsdns-28.co.uk 2600:9000:5306:e100::1	NOERROR, 9 ms, authoritative	no	yes / yes	refused	-
ns-50.awsdns-06.com 205.251.192.50	NOERROR, 9 ms, authoritative	no	yes / yes	refused	-
ns-50.awsdns-06.com 2600:9000:5300:3200::1	NOERROR, 9 ms, authoritative	no	yes / yes	refused	-
ns-758.awsdns-30.net 205.251.194.246	NOERROR, 4 ms, authoritative	no	yes / yes	refused	-
ns-758.awsdns-30.net 2600:9000:5302:f600::1	NOERROR, 5 ms, authoritative	no	yes / yes	refused	-

Checks

✓ All respond #14

All 8 nameserver addresses answered.
✓ All authoritative #15

Every responding nameserver answers authoritatively for the zone.
✓ No recursion #16

The nameservers do not answer recursive queries for other domains.
✓ No version disclosed #17

The nameservers don't reveal their software version.
✓ Zone transfers refused #18

No nameserver allows a zone transfer to the public.
✓ TCP supported #19

All nameservers answer over TCP.
✓ EDNS supported #20

All nameservers support EDNS(0).
✓ Public addresses #21

All nameserver addresses are publicly routable.

SOA

pass

serial 1 · primary ns-1761.awsdns-28.co.uk

Found

Primary (MNAME): ns-1761.awsdns-28.co.uk
Contact (RNAME): awsdns-hostmaster.amazon.com
Serial: 1
Refresh / retry: 7200 s / 900 s
Expire: 1209600 s
Negative TTL: 86400 s

Serial per nameserver

Nameserver	Serial
ns-1508.awsdns-60.org (205.251.197.228)	1
ns-1508.awsdns-60.org (2600:9000:5305:e400::1)	1
ns-1761.awsdns-28.co.uk (205.251.198.225)	1
ns-1761.awsdns-28.co.uk (2600:9000:5306:e100::1)	1
ns-50.awsdns-06.com (205.251.192.50)	1
ns-50.awsdns-06.com (2600:9000:5300:3200::1)	1
ns-758.awsdns-30.net (205.251.194.246)	1
ns-758.awsdns-30.net (2600:9000:5302:f600::1)	1

Checks

✓ Serial 1 everywhere #22

All nameservers serve the same version of the zone.
✓ Timers within recommendations #23

SOA refresh 2h, retry 15m, expire 14d, negative TTL 1d.
✓ Primary is a public nameserver #24

The primary nameserver ns-1761.awsdns-28.co.uk is one of the listed nameservers.
✓ Contact awsdns-hostmaster@amazon.com #25

The SOA RNAME awsdns-hostmaster.amazon.com means awsdns-hostmaster@amazon.com.
✓ Counter serial #26

The serial 1 is a plain counter.

DNSSEC

warn

Not signed

Found

Validated by resolver: no

Checks

!

Not signed

The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.

#27

Records

warn

41 records at the apex

Found

Read from: 205.251.197.228:53

Type	Value	TTL
SOA	ns-1761.awsdns-28.co.uk. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400	900
NS	ns-1508.awsdns-60.org.	172800
NS	ns-1761.awsdns-28.co.uk.	172800
NS	ns-50.awsdns-06.com.	172800
NS	ns-758.awsdns-30.net.	172800
A	52.222.136.78	60
A	52.222.136.15	60
A	52.222.136.79	60
A	52.222.136.5	60
MX	1 aspmx.l.google.com.	3600
MX	10 aspmx2.googlemail.com.	3600
MX	10 aspmx3.googlemail.com.	3600
MX	5 alt1.aspmx.l.google.com.	3600
MX	5 alt2.aspmx.l.google.com.	3600
TXT	" _globalsign-domain-verification=AF2GqyPRqAXSK-4QcLqN4teJxTb7G50mrqJq_SJXUS"	300
TXT	"MS=EBDF74D2F14BFA51776CAA8BCE5EE90221FCF0A3"	300
TXT	"ahrefs-site-verification_e25282a0c7ef0ec44e6b4449359d3a65fc7701fea55556323953973383dadd45"	300
TXT	"anthropic-domain-verification-p9drmc=KCJo7kZnafbWZCP9v3ZgfPSQo"	300
TXT	"apple-domain-verification=dnf4LToSxWblAonj"	300
TXT	"atlassian-sending-domain-verification=c44ddb67-c7e2-4f43-8cba-c3e035929d23"	300
TXT	"bw=pxwEWSvhbDeKp4TOfhCXrJmkGZOsTa9E3hSYp4f0E3E7"	300
TXT	"digicert-bimi=_q95p175uwlv37s31j33yi05wh5r600g"	300
TXT	"facebook-domain-verification=zengi5sn12igdvl3wqlrg9vrpkjbm8"	300
TXT	"figma-domain-verification=9a9027aac4c20fcb8a207e581eca7c1eb5bfb8d2f54e645fa1d331c1701248c6-1767851909"	300
TXT	"google-site-verification=T9W0PaUd4eXQbTEC20wj6zqXLikHHVyHTbQqZFoBDu0"	300
TXT	"google-site-verification=dzmO13a9cgx-3w-OADRBwDYxiHein8HmfaBdqmiZu1Q"	300
TXT	"google-site-verification=yGKj9BdcjkDVcOS48kYvlc9-sMF9p1hm-PlpFRZTiiw"	300
TXT	"hubspot-domain-verification=NGM4YmNkZTEtMGM3Yi00YzI1LTkyMzgtMmI5NmFlYzI3NzIx"	300
TXT	"jamf-site-verification=TOzPyjvrw8Fd34-qJwfy0g"	300
TXT	"linkedin-site-verification=5c883ad2-3e68-4c62-985b-b893fa8e093c"	300
TXT	"notion-domain-verification=Gt73NvwaJfEjiRSZG6tiJlp0X0NLKtS2RBYWrFXxNE7"	300
TXT	"onetrust-domain-verification=aeec4b0536d44ae5a1b81a57477657f6"	300
TXT	"openai-domain-verification=dv-31ZirJwknIdYldDxw7Oz0XzX"	300
TXT	"pinterest-site-verification=8c1d7f82194fab6dcf1e6a148e8687f1"	300
TXT	"v=spf1 include:_spf.google.com include:servers.mcsv.net include:mail.zendesk.com include:amazonses.com include:spf.mandrillapp.com include:26077024.spf07.hubspotemail.net include:spf.protection.outlook.com -all"	300
CAA	0 iodef "mailto:technical@mobilevikings.be"	300
CAA	0 issue "amazon.com"	300
CAA	0 issue "digicert.com"	300
CAA	0 issue "globalsign.com"	300
CAA	0 issue "letsencrypt.org"	300
CAA	0 issue "sectigo.com"	300

Checks

!

Very low TTLs

These records have a TTL below 5m, causing extra queries and slower lookups: A (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 2d; resolvers may use either.

#32
✓ No CNAME at the apex #33

The zone apex has no CNAME record.
i

Wildcard record

A random name under the zone resolves, so there is a wildcard (*) record. Typos and non-existent hosts resolve too, which can confuse mail and certificate checks.

#34
✓ CAA restricts issuance #35

Certificates may be issued by: amazon.com, digicert.com, globalsign.com, letsencrypt.org, sectigo.com.