Check DNS, Urls + Redirects, Certificates and Content of your Website


 

 

U

 

No dns entry found - perhaps mistype. Or wrong IDN

 

Checked:
14.04.2025 19:49:08

 

Older results

No older results found

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
moovexx.com

Server failure
yes
2
0
www.moovexx.com

Server failure
yes
2
0

 

2. DNSSEC

Zone (*)DNSSEC - Informations


Zone: (root)

(root)
1 DS RR published






DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest 4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=






Status: Valid because published






3 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 20326, Flags 257 (SEP = Secure Entry Point)






Public Key with Algorithm 8, KeyTag 38696, Flags 257 (SEP = Secure Entry Point)






Public Key with Algorithm 8, KeyTag 53148, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 02.05.2025, 00:00:00 +, Signature-Inception: 11.04.2025, 00:00:00 +, KeyTag 20326, Signer-Name: (root)






Status: Good - Algorithmus 8 and DNSKEY with KeyTag 20326 used to validate the DNSKEY RRSet






Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest "4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone



Zone: com

com
1 DS RR in the parent zone found






DS with Algorithm 13, KeyTag 19718, DigestType 2 and Digest isuwzSj0ElCoCkkTiUJNNBUi2Uaw2gwCkfLT13HXgFo=






1 RRSIG RR to validate DS RR found






RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 27.04.2025, 05:00:00 +, Signature-Inception: 14.04.2025, 04:00:00 +, KeyTag 53148, Signer-Name: (root)






Status: Good - Algorithmus 8 and DNSKEY with KeyTag 53148 used to validate the DS RRSet in the parent zone






3 DNSKEY RR found






Public Key with Algorithm 13, KeyTag 19718, Flags 257 (SEP = Secure Entry Point)






Public Key with Algorithm 13, KeyTag 23202, Flags 256






Public Key with Algorithm 13, KeyTag 40097, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner com., Algorithm: 13, 1 Labels, original TTL: 86400 sec, Signature-expiration: 27.04.2025, 14:02:35 +, Signature-Inception: 12.04.2025, 13:57:35 +, KeyTag 19718, Signer-Name: com






Status: Good - Algorithmus 13 and DNSKEY with KeyTag 19718 used to validate the DNSKEY RRSet






Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 19718, DigestType 2 and Digest "isuwzSj0ElCoCkkTiUJNNBUi2Uaw2gwCkfLT13HXgFo=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone



Zone: moovexx.com

moovexx.com
0 DS RR in the parent zone found






DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed query name "eied4vn0halk7rsesgh81sol7om3lf5l" between the hashed NSEC3-owner "eied4qdrlsgeq3kqi2d1qo6jrdng90dk" and the hashed NextOwner "eied82h0d8u50n8es44344csejl0irrj". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner eied4qdrlsgeq3kqi2d1qo6jrdng90dk.com., Algorithm: 13, 2 Labels, original TTL: 900 sec, Signature-expiration: 18.04.2025, 00:48:24 +, Signature-Inception: 10.04.2025, 23:38:24 +, KeyTag 23202, Signer-Name: com






DS-Query in the parent zone sends valid NSEC3 RR with the Hash "ck0pojmg874ljref7efn8430qvit8bsm" as Owner. That's the Hash of "com" with the NextHashedOwnerName "ck0q3udg8cekkae7rukpgct1dvssh8ll". So that domain name is the Closest Encloser of "moovexx.com". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner ck0pojmg874ljref7efn8430qvit8bsm.com., Algorithm: 13, 2 Labels, original TTL: 900 sec, Signature-expiration: 21.04.2025, 00:26:17 +, Signature-Inception: 13.04.2025, 23:16:17 +, KeyTag 23202, Signer-Name: com






0 DNSKEY RR found









Zone: www.moovexx.com

www.moovexx.com
0 DS RR in the parent zone found

 

3. Name Servers

DomainNameserverNS-IP
moovexx.com
  ns1.pedro.plugweb.com.br
162.214.152.121
Provo/Utah/United States (US) - Unified Layer


  ns2.pedro.plugweb.com.br
162.214.152.124
Provo/Utah/United States (US) - Unified Layer

com
  a.gtld-servers.net / nnn1-par6


  b.gtld-servers.net / nnn1-eltxl1


  c.gtld-servers.net / nnn1-par6


  d.gtld-servers.net / nnn1-par6


  e.gtld-servers.net / nnn1-par6


  f.gtld-servers.net / nnn1-defra-4


  g.gtld-servers.net / nnn1-defra-4


  h.gtld-servers.net / nnn1-defra-4


  i.gtld-servers.net / nnn1-defra-4


  j.gtld-servers.net / nnn1-frmrs-2


  k.gtld-servers.net / nnn1-frmrs-2


  l.gtld-servers.net / nnn1-frmrs-2


  m.gtld-servers.net / nnn1-frmrs-2

 

4. SOA-Entries


Domain:com
Zone-Name:com
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1744652930
Refresh:1800
Retry:900
Expire:604800
TTL:900
num Entries:10


Domain:com
Zone-Name:com
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1744652945
Refresh:1800
Retry:900
Expire:604800
TTL:900
num Entries:3


Domain:moovexx.com
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:2


5. Screenshots

No Screenshot listed, because no url-check with https + http status 200-299, 400-599 + not-ACME-check found.

 

 

6. Url-Checks

DomainnameHttp-StatusredirectSec.G








 

7. Comments


1. General Results, most used to calculate the result

Aname "moovexx.com" is domain, public suffix is ".com", top-level-domain is ".com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .com-domains preloaded: 105479 (complete: 270180)
AGood: No asked Authoritative Name Server had a timeout
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
XFatal error: Nameserver doesn't support TCP connection: ns1.pedro.plugweb.com.br / 162.214.152.121: ServerFailure
XFatal error: Nameserver doesn't support TCP connection: ns2.pedro.plugweb.com.br / 162.214.152.124: ServerFailure
BNo _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Read the result of server-daten.de (Url-Checks, Comments, Connections and DomainServiceRecords) to see a complete definition. Domainname: _mta-sts.moovexx.com

2. Header-Checks

U

No https result with http status 2** or 4** (standard-check) found, no header checked.

3. DNS- and NameServer - Checks

A
A
AInfo:: 13 different Name Servers found: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net, 13 Name Servers included in Delegation: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net, 13 Name Servers included in 1 Zone definitions: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net, 1 Name Servers listed in SOA.Primary: a.gtld-servers.net.
AGood: Only one SOA.Primary Name Server found.: a.gtld-servers.net.
AGood: SOA.Primary Name Server included in the delegation set.: a.gtld-servers.net.
AGood: All Name Server Domain Names have a Public Suffix.
A
AGood: Nameserver supports Echo Capitalization: 2 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 13 good Nameserver
Nameserver doesn't pass all EDNS-Checks: ns1.pedro.plugweb.com.br / 162.214.152.121: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns2.pedro.plugweb.com.br / 162.214.152.124: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok.
AGood: All SOA have the same Serial Number
Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries.

4. Content- and Performance-critical Checks

Info: Creating a Letsencrypt certificate with that domain name isn't possible. To create a certificate you need a registered, worldwide unique domain name. The domain name ends with a public suffix, that's good (not Grade Z). But the domain isn't registered. If you want a certificate with that domain name, you have to proof that you are the domain owner. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
AGood: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx
ADuration: 56410 milliseconds, 56.410 seconds

 

8. Connections

No connection informations found. Perhaps only http - connections.

 

9. Certificates

No certificate informations found. Perhaps only http - connections.

 

10. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates (one check per day)

Issuerlast 7 daysactivenum Certs
//certs.godaddy.com/repository/, CN=Go Daddy Secure Certificate Authority - G2
0
2
2
CN=R10, O=Let's Encrypt, C=US
0
0
1

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
9299543802
precert
//certs.godaddy.com/repository/, CN=Go Daddy Secure Certificate Authority - G2
2025-01-23 11:49:09
2026-01-23 11:49:09
moovexx.com - 1 entries


9296665288
leaf cert
//certs.godaddy.com/repository/, CN=Go Daddy Secure Certificate Authority - G2
2025-01-23 04:06:47
2026-01-23 04:06:47
www.moovexx.com - 1 entries


9239319673
leaf cert
CN=R10, O=Let's Encrypt, C=US
2025-01-17 02:08:00
2025-04-17 02:07:59
*.moovexx.com, moovexx.com - 2 entries


 

2. Source crt.sh - old and new certificates, sometimes very slow - only certificates with "not after" > of the last months are listed

Issuerlast 7 daysactivenum Certs
//certs.godaddy.com/repository/, CN=Go Daddy Secure Certificate Authority - G2
0
2
2
CN=R10, O=Let's Encrypt, C=US
0
0
2

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
16376412003
precert
//certs.godaddy.com/repository/, CN=Go Daddy Secure Certificate Authority - G2
2025-01-23 10:49:09
2026-01-23 10:49:09
moovexx.com
1 entries


16374767111
precert
//certs.godaddy.com/repository/, CN=Go Daddy Secure Certificate Authority - G2
2025-01-23 03:06:47
2026-01-23 03:06:47
www.moovexx.com
1 entries


16647934342
leaf cert
CN=R10, O=Let's Encrypt, C=US
2025-01-17 01:08:00
2025-04-17 00:07:59
*.moovexx.com, moovexx.com
2 entries


15519152103
leaf cert
CN=R10, O=Let's Encrypt, C=US
2024-11-17 23:08:09
2025-02-15 23:08:08
*.moovexx.com, moovexx.com
2 entries


 

11. Html-Content - Entries

No Html-Content entries found. Only checked if https + status 200/401/403/404

 

12. Html-Parsing via https://validator.w3.org/nu/


No https result http status 200 and Content-Type text/html or text/xml found, no Html-Parsing - Check

 

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers:

 

 

No NameServer - IP address - Informations found

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
moovexx.com
-2

Server failure - The name server was unable to process this query due to a problem with the name server
2
0
com
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
moovexx.com

Server failure - The name server was unable to process this query due to a problem with the name server
2
0
moovexx.com

Server failure - The name server was unable to process this query due to a problem with the name server
2
0
_acme-challenge.moovexx.com

Server failure - The name server was unable to process this query due to a problem with the name server
3
0
_acme-challenge.moovexx.com

Server failure - The name server was unable to process this query due to a problem with the name server
3
0
_acme-challenge.moovexx.com

Server failure - The name server was unable to process this query due to a problem with the name server
3
0
_acme-challenge.moovexx.com.moovexx.com

Server failure - The name server was unable to process this query due to a problem with the name server
2
0
_acme-challenge.moovexx.com.moovexx.com

Server failure - The name server was unable to process this query due to a problem with the name server
2
0

 

16. DomainService - Entries

No DomainServiceEntries entries found

 

 

17. Cipher Suites

No Ciphers found

 

18. Portchecks

No open Ports <> 80 / 443 found, so no additional Ports checked.

 

 

Permalink: https://check-your-website.server-daten.de/?i=17b46dda-86c1-491c-b5d5-b40e8853e868

 

Last Result: https://check-your-website.server-daten.de/?q=moovexx.com - 2025-04-14 19:49:08

 

Do you like this page? Support this tool, add a link on your page:

 

<a href="https://check-your-website.server-daten.de/?q=moovexx.com" target="_blank">Check this Site: moovexx.com</a>

 

 

Do you really want to support this project? Donate: Check-your-website, IBAN DE98 1001 0010 0575 2211 07, SWIFT/BIC PBNKDEFF, Euro

 

QR-Code of this page - https://check-your-website.server-daten.de/?d=moovexx.com