livecasinoau.com

Checked 22 October 2026, 09:40 UTC · via 8.8.8.8
!Passed with warnings
21 passed 4 warnings 0 failed 6 info

Registration

info

.com generic · GoDaddy.com, LLC · expires 2027-08-31

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
GoDaddy.com, LLC
Registered
31 August 2020
Last changed
12 October 2026
Expires
31 August 2027
Status
client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
Registry nameservers
ns2.expirationwarning.net, ns6.expirationwarning.net
RDAP server
https://rdap.verisign.com/com/v1/

Checks

  • i
    .com is a generic TLD (gTLD)
    Generic TLD under an ICANN registry agreement: ICANN-accredited registrars, UDRP and RDAP apply.
    #1
  • ✓ TLD delegated and signed #2
    .com is delegated in the root zone and DNSSEC-signed.
  • ✓ Expires on 2027-08-31 #3
    The registration is valid until 2027-08-31 (313 days).
  • ✓ Transfer locked #4
    Registry status: client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

warn

ns2.expirationwarning.net, ns6.expirationwarning.net

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns2.expirationwarning.net, ns6.expirationwarning.net
NS in the zone
ns2.expirationwarning.net, ns6.expirationwarning.net
NameserverAddressesNetwork (AS)Glue
ns2.expirationwarning.net54.38.216.42AS16276 OVH - OVH SAS, FR-
ns6.expirationwarning.net142.44.169.83AS16276 OVH - OVH SAS, FR-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns2.expirationwarning.net, ns6.expirationwarning.net.
    #6
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ 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 2 IPv4 /24s and 0 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS16276 (OVH - OVH SAS, FR): 2 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • i
    All nameserver names under .net
    All nameserver names are under one TLD, so a problem with that TLD also makes the nameservers unreachable. Some operators use names under two TLDs for extra resilience.
    #12
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

warn

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns2.expirationwarning.net 54.38.216.42NOERROR, 5 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.5.3
ns6.expirationwarning.net 142.44.169.83NOERROR, 97 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.5.3

Checks

  • ✓ All respond #14
    All 2 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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns2.expirationwarning.net: "PowerDNS Authoritative Server 4.5.3"; ns6.expirationwarning.net: "PowerDNS Authoritative Server 4.5.3". Hide or replace the version string.
    #17
  • ✓ 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

warn

serial 2026070800 · primary ns2.expirationwarning.net

Found

Primary (MNAME)
ns2.expirationwarning.net
Contact (RNAME)
hostmaster.expirationwarning.net
Serial
2026070800
Refresh / retry
7200 s / 3600 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns2.expirationwarning.net (54.38.216.42)2026070800
ns6.expirationwarning.net (142.44.169.83)2026070900

Checks

  • !
    Serials differ
    The nameservers serve different versions of the zone: 2026070800 on ns2.expirationwarning.net (54.38.216.42); 2026070900 on ns6.expirationwarning.net (142.44.169.83). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.
    #22
  • ✓ Timers within recommendations #23
    SOA refresh 2h, retry 1h, expire 7d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns2.expirationwarning.net is one of the listed nameservers.
  • ✓ Contact hostmaster@expirationwarning.net #25
    The SOA RNAME hostmaster.expirationwarning.net means hostmaster@expirationwarning.net.
  • ✓ Date-based serial #26
    The serial 2026070800 follows the YYYYMMDDnn convention (2026-07-08).

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

info

4 records at the apex

Found

Read from
54.38.216.42:53
TypeValueTTL
SOAns2.expirationwarning.net. hostmaster.expirationwarning.net. 2026070800 7200 3600 604800 36003600
NSns2.expirationwarning.net.3600
NSns6.expirationwarning.net.3600
A54.38.216.423600

Checks

  • ✓ TTLs within range #32
    TTLs: A 1h, NS 1h. The NS TTL at the parent is 2d and in the zone 1h; resolvers may use either.
  • ✓ 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
  • i
    No CAA records
    Without CAA records any certificate authority may issue certificates for this domain. A CAA record limits issuance to the CAs you use.
    #35