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


 

 

Y

 

Private IP-Address found

 

Checked:
03.10.2025 14:41:10

 

Older results

 

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
gitlab.esla.com
A
192.168.0.248
No Hostname found
yes
1
0

AAAA

yes


www.gitlab.esla.com

Name Error
yes
1
0
*.esla.com
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


*.gitlab.esla.com
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


 

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






4 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 46441, Flags 256






Public Key with Algorithm 8, KeyTag 61809, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 22.10.2025, 00:00:00 +, Signature-Inception: 01.10.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: 16.10.2025, 05:00:00 +, Signature-Inception: 03.10.2025, 04:00:00 +, KeyTag 61809, Signer-Name: (root)






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






2 DNSKEY RR found






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






Public Key with Algorithm 13, KeyTag 20545, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner com., Algorithm: 13, 1 Labels, original TTL: 86400 sec, Signature-expiration: 14.10.2025, 14:02:35 +, Signature-Inception: 29.09.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: esla.com

esla.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 "l5u9rrnqj8976i0j6798ss0if26c03p6" between the hashed NSEC3-owner "l5u9keea5lpih7rbph9hsjaltkpmce6p" and the hashed NextOwner "l5ua5p346sb6q0ovjv4cj8mt97cn76jm". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner l5u9keea5lpih7rbph9hsjaltkpmce6p.com., Algorithm: 13, 2 Labels, original TTL: 900 sec, Signature-expiration: 09.10.2025, 01:40:59 +, Signature-Inception: 02.10.2025, 00:30:59 +, KeyTag 20545, 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 "esla.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: 10.10.2025, 00:26:19 +, Signature-Inception: 02.10.2025, 23:16:19 +, KeyTag 20545, Signer-Name: com






0 DNSKEY RR found









Zone: gitlab.esla.com

gitlab.esla.com
0 DS RR in the parent zone found






0 DNSKEY RR found









Zone: www.gitlab.esla.com

www.gitlab.esla.com
0 DS RR in the parent zone found

 

3. Name Servers

DomainNameserverNS-IP
www.gitlab.esla.com
  dns7.servidoresdns.net

gitlab.esla.com
  dns7.servidoresdns.net
217.76.128.131
Logroño/La Rioja/Spain (ES) - arsys.es

esla.com
  dns7.servidoresdns.net
217.76.128.131
Logroño/La Rioja/Spain (ES) - arsys.es


  dns8.servidoresdns.net
82.223.218.135
Madrid/Spain (ES) - arsys.es

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


  b.gtld-servers.net / nnn1-elwaw4


  c.gtld-servers.net / nnn1-par6


  d.gtld-servers.net / nnn1-par6


  e.gtld-servers.net / nnn1-par6


  f.gtld-servers.net / nnn1-ham1


  g.gtld-servers.net / nnn1-ham4


  h.gtld-servers.net / nnn1-wie3


  i.gtld-servers.net / nnn1-ham5


  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:1759495239
Refresh:1800
Retry:900
Expire:604800
TTL:900
num Entries:1


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


Domain:esla.com
Zone-Name:esla.com
Primary:dns7.servidoresdns.net
Mail:hostmaster.servidoresdns.net
Serial:2002092864
Refresh:21600
Retry:3600
Expire:2419200
TTL:86400
num Entries:2


Domain:gitlab.esla.com
Zone-Name:esla.com
Primary:dns7.servidoresdns.net
Mail:hostmaster.servidoresdns.net
Serial:2002092864
Refresh:21600
Retry:3600
Expire:2419200
TTL:86400
num Entries:1


Domain:www.gitlab.esla.com
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


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 "gitlab.esla.com" is subdomain, 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: 108094 (complete: 276475)
AGood: No asked Authoritative Name Server had a timeout
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
Ygitlab.esla.com

192.168.0.248
Warning: Private ip address found. No connection possible. There are two types of ip addresses: Worldwide unique, global addresses and private addresses. If you want that other users connect your domain, your domain must have minimal one A- (ipv4) or AAAA- (ipv6) entry with a global ip address. Check https://en.wikipedia.org/wiki/Private_network to understand the details: 192.168.0.0 to 192.168.255.255: Class C - 256 private net, every with 256 addresses
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.gitlab.esla.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

AInfo:: 7 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 7 Queries complete, 3 with IPv6, 4 with IPv4.
Warning: Only some DNS Queries done via ipv6. IPv6 is the future, so the name servers of your name servers should have ipv6 addresses.
Ok (4 - 8):: An average of 3.5 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 2 different Name Servers found: dns7.servidoresdns.net, dns8.servidoresdns.net, 2 Name Servers included in Delegation: dns7.servidoresdns.net, dns8.servidoresdns.net, 2 Name Servers included in 1 Zone definitions: dns7.servidoresdns.net, dns8.servidoresdns.net, 1 Name Servers listed in SOA.Primary: dns7.servidoresdns.net.
AGood: Only one SOA.Primary Name Server found.: dns7.servidoresdns.net.
AGood: SOA.Primary Name Server included in the delegation set.: dns7.servidoresdns.net.
AGood: Consistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Ordered list of name servers: dns7.servidoresdns.net, dns8.servidoresdns.net
AGood: All Name Server Domain Names have a Public Suffix.
AGood: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
AGood: All Name Server ip addresses are public.
AGood: Minimal 2 different name servers (public suffix and public ip address) found: 2 different Name Servers found
Warning: No Name Server IPv6 address found. IPv6 is the future, so your name servers should be visible via IPv6.: 2 different Name Servers found
Warning: All Name Servers have the same Top Level Domain / Public Suffix. If there is a problem with that Top Level Domain, your domain may be affected. Better: Use Name Servers with different top level domains.: 2 Name Servers, 1 Top Level Domain: net
Warning: All Name Servers have the same domain name. If there is a problem with that domain name (or with the name servers of that domain name), your domain may be affected. Better: Use Name Servers with different domain names / different top level domains.: Only one domain name used: servidoresdns.net
Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: ES
AInfo: Ipv4-Subnet-list: 2 Name Servers, 2 different subnets (first Byte): 217., 82., 2 different subnets (first two Bytes): 217.76., 82.223., 2 different subnets (first three Bytes): 217.76.128., 82.223.218.
AExcellent: Every Name Server IPv4-address starts with an unique Byte.
AGood: Nameserver supports TCP connections: 1 good Nameserver
AGood: Nameserver supports Echo Capitalization: 1 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 1 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 1 good Nameserver
Nameserver doesn't pass all EDNS-Checks: dns7.servidoresdns.net: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
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

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: 93766 milliseconds, 93.766 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)

No CertSpotter - CT-Log entries found

 

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

No CRT - CT-Log entries found

 

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: dns7.servidoresdns.net, dns8.servidoresdns.net

 

QNr.DomainTypeNS used
1
net
NS
b.root-servers.net (2001:500:200::b)

Answer: 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
2
dns7.servidoresdns.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: atlante.servidoresdns.net, menecio.servidoresdns.net, prometeo.servidoresdns.net

Answer: atlante.servidoresdns.net
217.76.128.10

Answer: menecio.servidoresdns.net
2001:ba0:3:100::100, 82.223.218.4

Answer: prometeo.servidoresdns.net
82.223.191.10
3
dns8.servidoresdns.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: atlante.servidoresdns.net, menecio.servidoresdns.net, prometeo.servidoresdns.net

Answer: atlante.servidoresdns.net
217.76.128.10

Answer: menecio.servidoresdns.net
2001:ba0:3:100::100, 82.223.218.4

Answer: prometeo.servidoresdns.net
82.223.191.10
4
dns7.servidoresdns.net: 217.76.128.131
A
atlante.servidoresdns.net (217.76.128.10)
5
dns7.servidoresdns.net: No AAAA record found
AAAA
atlante.servidoresdns.net (217.76.128.10)
6
dns8.servidoresdns.net: 82.223.218.135
A
atlante.servidoresdns.net (217.76.128.10)
7
dns8.servidoresdns.net: No AAAA record found
AAAA
atlante.servidoresdns.net (217.76.128.10)

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
gitlab.esla.com
0

no CAA entry found
1
0
esla.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
esla.com
202106090709133m2z7ejkzcchibbxge1wses0wqjb21o2d1gxq0pkbplevknhcy
ok
1
0
esla.com
facebook-domain-verification=5j4bwciwr7y3n9s4c6wdlqhva81zhx
ok
1
0
esla.com
google-site-verification=-52-K5bgv_Nf_rMnbdwHWjEjJIocOognp4S7_Dk_iKs
ok
1
0
esla.com
google-site-verification=FLY2HD7jKIc5W69L7Li-80vblvx2gbxAPGJqtculo2A
ok
1
0
esla.com
google-site-verification=FLY2HD7jKlc5W69L7Li-8Ovblvx2gbxAPGJqtculo2A
ok
1
0
esla.com
google-site-verification=GD7yZ7oBQV8iwv2eNtExv2ZHMDlHgOw73v4JS1RD22E
ok
1
0
esla.com
MS=1AE8BB58B32A306EDCEC28CA988976ACBFC481CE
ok
1
0
esla.com
v=spf1 include:_spf.serviciodecorreo.es ~all
ok
1
0
gitlab.esla.com

ok
1
0
_acme-challenge.gitlab.esla.com

Name Error - The domain name does not exist
1
0
_acme-challenge.gitlab.esla.com.esla.com

Name Error - The domain name does not exist
1
0
_acme-challenge.gitlab.esla.com.gitlab.esla.com

Name Error - The domain name does not exist
1
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=91c14bd0-da71-4519-93b0-d61009f2bc0f

 

Last Result: https://check-your-website.server-daten.de/?q=gitlab.esla.com - 2025-10-03 14:41:10

 

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

 

<a href="https://check-your-website.server-daten.de/?q=gitlab.esla.com" target="_blank">Check this Site: gitlab.esla.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=gitlab.esla.com