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



V

Connect failure - perhaps firewall

Checked:
23.02.2021 11:50:48


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
digydia.com
A
151.80.58.190
Roubaix/Hauts-de-France/France (FR) - OVH SAS
Hostname: vps-1cb20310.vps.ovh.net
yes
1
0

AAAA
2001:41d0:302:2200::2905
Paris/Île-de-France/France (FR) - OVH SAS

yes


www.digydia.com
A
151.80.58.190
Roubaix/Hauts-de-France/France (FR) - OVH SAS
Hostname: vps-1cb20310.vps.ovh.net
yes
1
0

AAAA
2001:41d0:302:2200::2905
Paris/Île-de-France/France (FR) - OVH SAS

yes


*.digydia.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



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 42351, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 13.03.2021, 00:00:00 +, Signature-Inception: 20.02.2021, 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 8, KeyTag 30909, DigestType 2 and Digest 4tPJFvbe6scylOgmj7WIUESoM/xUWViPSpGEz8QaV2Y=



1 RRSIG RR to validate DS RR found



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



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



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 58540, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 06.03.2021, 19:24:21 +, Signature-Inception: 19.02.2021, 19:19:21 +, KeyTag 30909, Signer-Name: com



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



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

Zone: digydia.com
digydia.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 "po9mq0nmbdks56fvm0g5fas19u3vu79q" between the hashed NSEC3-owner "po9m59q9cn282n5imv2e3tmftgqgv74u" and the hashed NextOwner "po9ng3r48b9gib6c05hq7rik6m5pa5dg". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner po9m59q9cn282n5imv2e3tmftgqgv74u.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 01.03.2021, 06:09:01 +, Signature-Inception: 22.02.2021, 04:59:01 +, KeyTag 58540, 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 "ck0q1gin43n1arrc9osm6qpqr81h5m9a". So that domain name is the Closest Encloser of "digydia.com". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner ck0pojmg874ljref7efn8430qvit8bsm.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 01.03.2021, 05:40:44 +, Signature-Inception: 22.02.2021, 04:30:44 +, KeyTag 58540, Signer-Name: com



0 DNSKEY RR found




Zone: www.digydia.com
www.digydia.com
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.digydia.com
  dns105.ovh.net

digydia.com
  dns105.ovh.net
213.251.188.149
Roubaix/Hauts-de-France/France (FR) - OVH ISP


 
2001:41d0:1:4a95::1
Roubaix/Hauts-de-France/France (FR) - OVH SAS


  ns105.ovh.net
213.251.128.149
Paris/Île-de-France/France (FR) - OVH SAS


 
2001:41d0:1:1995::1
Roubaix/Hauts-de-France/France (FR) - OVH SAS

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


  b.gtld-servers.net / nnn1-eltxl2


  c.gtld-servers.net / nnn1-fra8


  d.gtld-servers.net / nnn1-fra8


  e.gtld-servers.net / nnn1-fra8


  f.gtld-servers.net / nnn1-fra5


  g.gtld-servers.net / nnn1-fra5


  h.gtld-servers.net / nnn1-fra5


  i.gtld-servers.net / nnn1-fra5


  j.gtld-servers.net / nnn1-ein5


  k.gtld-servers.net / nnn1-ein3


  l.gtld-servers.net / nnn1-ein1


  m.gtld-servers.net / nnn1-ein5


4. SOA-Entries


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


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


Domain:digydia.com
Zone-Name:digydia.com
Primary:dns105.ovh.net
Mail:tech.ovh.net
Serial:2021022201
Refresh:86400
Retry:3600
Expire:3600000
TTL:300
num Entries:4


Domain:www.digydia.com
Zone-Name:digydia.com
Primary:dns105.ovh.net
Mail:tech.ovh.net
Serial:2021022201
Refresh:86400
Retry:3600
Expire:3600000
TTL:300
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
• http://digydia.com/
151.80.58.190
-2

1.077
V
ConnectFailure - Unable to connect to the remote server

• http://digydia.com/
2001:41d0:302:2200::2905
-14

10.017
T
Timeout - The operation has timed out

• http://www.digydia.com/
151.80.58.190
-2

1.067
V
ConnectFailure - Unable to connect to the remote server

• http://www.digydia.com/
2001:41d0:302:2200::2905
-14

10.024
T
Timeout - The operation has timed out

• https://digydia.com/
151.80.58.190
-2

1.077
V
ConnectFailure - Unable to connect to the remote server

• https://digydia.com/
2001:41d0:302:2200::2905
-14

10.030
T
Timeout - The operation has timed out

• https://www.digydia.com/
151.80.58.190
-2

1.074
V
ConnectFailure - Unable to connect to the remote server

• https://www.digydia.com/
2001:41d0:302:2200::2905
-14

10.037
T
Timeout - The operation has timed out

• http://digydia.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
151.80.58.190
-2

1.077
V
ConnectFailure - Unable to connect to the remote server
Visible Content:

• http://digydia.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
2001:41d0:302:2200::2905
-14

10.030
T
Timeout - The operation has timed out
Visible Content:

• http://www.digydia.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
151.80.58.190
-2

1.090
V
ConnectFailure - Unable to connect to the remote server
Visible Content:

• http://www.digydia.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
2001:41d0:302:2200::2905
-14

10.030
T
Timeout - The operation has timed out
Visible Content:

• https://151.80.58.190/
151.80.58.190
-2

1.083
V
ConnectFailure - Unable to connect to the remote server

• https://[2001:41d0:0302:2200:0000:0000:0000:2905]/
2001:41d0:302:2200::2905
-14

10.034
T
Timeout - The operation has timed out

7. Comments


1. General Results, most used to calculate the result

Aname "digydia.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: 55723 (complete: 142558)
Agood: All ip addresses are public addresses
AGood: Minimal 2 ip addresses per domain name found: digydia.com has 2 different ip addresses (authoritative).
AGood: Minimal 2 ip addresses per domain name found: www.digydia.com has 2 different ip addresses (authoritative).
AGood: Ipv4 and Ipv6 addresses per domain name found: digydia.com has 1 ipv4, 1 ipv6 addresses
AGood: Ipv4 and Ipv6 addresses per domain name found: www.digydia.com has 1 ipv4, 1 ipv6 addresses
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.
Khttp://digydia.com/ 151.80.58.190, Status -2

http://digydia.com/ 2001:41d0:302:2200::2905, Status -14
configuration problem - different ip addresses with different status
Khttp://www.digydia.com/ 151.80.58.190, Status -2

http://www.digydia.com/ 2001:41d0:302:2200::2905, Status -14
configuration problem - different ip addresses with different status
Khttps://digydia.com/ 151.80.58.190, Status -2

https://digydia.com/ 2001:41d0:302:2200::2905, Status -14
configuration problem - different ip addresses with different status
Khttps://www.digydia.com/ 151.80.58.190, Status -2

https://www.digydia.com/ 2001:41d0:302:2200::2905, Status -14
configuration problem - different ip addresses with different status
Khttp://digydia.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 151.80.58.190, Status -2

http://digydia.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:41d0:302:2200::2905, Status -14
configuration problem - different ip addresses with different status
Khttp://www.digydia.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 151.80.58.190, Status -2

http://www.digydia.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:41d0:302:2200::2905, Status -14
configuration problem - different ip addresses with different status
Vhttp://digydia.com/ 151.80.58.190
-2

connect failure - perhaps firewall
Vhttp://www.digydia.com/ 151.80.58.190
-2

connect failure - perhaps firewall
Vhttps://digydia.com/ 151.80.58.190
-2

connect failure - perhaps firewall
Vhttps://www.digydia.com/ 151.80.58.190
-2

connect failure - perhaps firewall
Vhttp://digydia.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 151.80.58.190
-2

connect failure - perhaps firewall
Vhttp://www.digydia.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 151.80.58.190
-2

connect failure - perhaps firewall
Vhttps://151.80.58.190/ 151.80.58.190
-2

connect failure - perhaps firewall
AGood: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain digydia.com, 2 ip addresses.
AGood: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain www.digydia.com, 2 ip addresses.
Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain digydia.com, 2 ip addresses.
Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain www.digydia.com, 2 ip addresses.

2. DNS- and NameServer - Checks

AInfo:: 16 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 16 Queries complete, 16 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
Ok (4 - 8):: An average of 8.0 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 2 different Name Servers found: dns105.ovh.net, ns105.ovh.net, 2 Name Servers included in Delegation: dns105.ovh.net, ns105.ovh.net, 2 Name Servers included in 1 Zone definitions: dns105.ovh.net, ns105.ovh.net, 1 Name Servers listed in SOA.Primary: dns105.ovh.net.
AGood: Only one SOA.Primary Name Server found.: dns105.ovh.net.
AGood: SOA.Primary Name Server included in the delegation set.: dns105.ovh.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: dns105.ovh.net, ns105.ovh.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
AGood: All name servers have ipv4- and ipv6-addresses.: 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: ovh.net
Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: FR
AInfo: Ipv4-Subnet-list: 2 Name Servers, 1 different subnets (first Byte): 213., 1 different subnets (first two Bytes): 213.251., 2 different subnets (first three Bytes): 213.251.128., 213.251.188.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2001:, 1 different subnets (first two blocks): 2001:41d0:, 1 different subnets (first three blocks): 2001:41d0:0001:, 2 different subnets (first four blocks): 2001:41d0:0001:1995:, 2001:41d0:0001:4a95:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 4 good Nameserver
AGood: Nameserver supports Echo Capitalization: 4 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 4 good Nameserver
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.

3. Content- and Performance-critical Checks

http://digydia.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:41d0:302:2200::2905
-14

Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://www.digydia.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:41d0:302:2200::2905
-14

Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://digydia.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 151.80.58.190
-2

Fatal: Check of /.well-known/acme-challenge/random-filename is blocked, http connection error. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://www.digydia.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 151.80.58.190
-2

Fatal: Check of /.well-known/acme-challenge/random-filename is blocked, http connection error. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://digydia.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:41d0:302:2200::2905, Status -14

http://digydia.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 151.80.58.190, Status -2
Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>. If you use IIS, check your bindings. Don't select a single ip address. Use this tool to check your raw ipv6 address. Add your domain name in the "Hostname" - field. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://www.digydia.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:41d0:302:2200::2905, Status -14

http://www.digydia.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 151.80.58.190, Status -2
Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>. If you use IIS, check your bindings. Don't select a single ip address. Use this tool to check your raw ipv6 address. Add your domain name in the "Hostname" - field. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
AInfo: No img element found, no alt attribute checked
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: 137990 milliseconds, 137.990 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
CN=R3, O=Let's Encrypt, C=US
0
8
8
CN=Cloudflare Inc ECC CA-3, O="Cloudflare, Inc.", C=US
0
2
2
CN=Cloudflare Inc RSA CA-2, O="Cloudflare, Inc.", C=US
0
2
2

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
2318192410
leaf cert
CN=R3, O=Let's Encrypt, C=US
2021-02-22 23:11:33
2021-05-23 23:11:33
digydia.com, www.digydia.com - 2 entries


2318124924
leaf cert
CN=R3, O=Let's Encrypt, C=US
2021-02-22 22:31:09
2021-05-23 22:31:09
www.digydia.com - 1 entries


2318096695
leaf cert
CN=R3, O=Let's Encrypt, C=US
2021-02-22 22:12:47
2021-05-23 22:12:47
digydia.com - 1 entries


2318090467
leaf cert
CN=R3, O=Let's Encrypt, C=US
2021-02-22 22:09:34
2021-05-23 22:09:34
digydia.com - 1 entries


2318073386
leaf cert
CN=R3, O=Let's Encrypt, C=US
2021-02-22 22:04:06
2021-05-23 22:04:06
digydia.com - 1 entries


2318063681
leaf cert
CN=R3, O=Let's Encrypt, C=US
2021-02-22 21:55:11
2021-05-23 21:55:11
digydia.com - 1 entries


2317945325
leaf cert
CN=R3, O=Let's Encrypt, C=US
2021-02-22 20:35:11
2021-05-23 20:35:11
digydia.com - 1 entries


2187360392
leaf cert
CN=R3, O=Let's Encrypt, C=US
2021-01-03 21:59:33
2021-04-03 21:59:33
digydia.com, www.digydia.com - 2 entries


1736906528
precert
CN=Cloudflare Inc ECC CA-3, O="Cloudflare, Inc.", C=US
2020-07-03 00:00:00
2021-07-03 12:00:00
www.digydia.com - 1 entries


1736906621
precert
CN=Cloudflare Inc RSA CA-2, O="Cloudflare, Inc.", C=US
2020-07-03 00:00:00
2021-07-03 12:00:00
www.digydia.com - 1 entries


1734796138
precert
CN=Cloudflare Inc RSA CA-2, O="Cloudflare, Inc.", C=US
2020-07-02 00:00:00
2021-07-02 12:00:00
www.digydia.com - 1 entries


1734796507
precert
CN=Cloudflare Inc ECC CA-3, O="Cloudflare, Inc.", C=US
2020-07-02 00:00:00
2021-07-02 12:00:00
www.digydia.com - 1 entries



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

Issuerlast 7 daysactivenum Certs
CN=R3, O=Let's Encrypt, C=US
0 /0 new
8
8
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
0 /0 new
0
6
CN=Cloudflare Inc ECC CA-3, O="Cloudflare, Inc.", C=US
0
2
2
CN=Cloudflare Inc RSA CA-2, O="Cloudflare, Inc.", C=US
0
2
2
CN=CloudFlare Inc ECC CA-2, O="CloudFlare, Inc.", L=San Francisco, C=US, ST=CA
0
0
1
CN=CloudFlare Inc RSA CA-1, O="CloudFlare, Inc.", L=San Francisco, C=US, ST=CA
0
0
1

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
4118303484
leaf cert
CN=R3, O=Let's Encrypt, C=US
2021-02-22 22:11:33
2021-05-23 21:11:33
digydia.com, www.digydia.com
2 entries


4118154373
leaf cert
CN=R3, O=Let's Encrypt, C=US
2021-02-22 21:31:09
2021-05-23 20:31:09
www.digydia.com
1 entries


4118091748
precert
CN=R3, O=Let's Encrypt, C=US
2021-02-22 21:12:47
2021-05-23 20:12:47
digydia.com
1 entries


4118078562
precert
CN=R3, O=Let's Encrypt, C=US
2021-02-22 21:09:34
2021-05-23 20:09:34
digydia.com
1 entries


4118060252
leaf cert
CN=R3, O=Let's Encrypt, C=US
2021-02-22 21:04:06
2021-05-23 20:04:06
digydia.com
1 entries


4118033507
precert
CN=R3, O=Let's Encrypt, C=US
2021-02-22 20:55:11
2021-05-23 19:55:11
digydia.com
1 entries


4117811126
precert
CN=R3, O=Let's Encrypt, C=US
2021-02-22 19:35:11
2021-05-23 18:35:11
digydia.com
1 entries


3872749568
precert
CN=R3, O=Let's Encrypt, C=US
2021-01-03 20:59:33
2021-04-03 19:59:33
digydia.com, www.digydia.com
2 entries


3603729362
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-11-04 19:52:42
2021-02-02 19:52:42
digydia.com, www.digydia.com
2 entries


3342180189
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-09-05 17:38:38
2020-12-04 18:38:38
digydia.com, www.digydia.com
2 entries


3055100953
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-07-07 17:19:22
2020-10-05 17:19:22
digydia.com, www.digydia.com
2 entries


3033978701
precert
CN=Cloudflare Inc ECC CA-3, O="Cloudflare, Inc.", C=US
2020-07-02 22:00:00
2021-07-03 10:00:00
www.digydia.com
1 entries


3033978814
precert
CN=Cloudflare Inc RSA CA-2, O="Cloudflare, Inc.", C=US
2020-07-02 22:00:00
2021-07-03 10:00:00
www.digydia.com
1 entries


3030549502
precert
CN=Cloudflare Inc RSA CA-2, O="Cloudflare, Inc.", C=US
2020-07-01 22:00:00
2021-07-02 10:00:00
www.digydia.com
1 entries


3030550323
precert
CN=Cloudflare Inc ECC CA-3, O="Cloudflare, Inc.", C=US
2020-07-01 22:00:00
2021-07-02 10:00:00
www.digydia.com
1 entries


2920466937
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-05-30 14:49:54
2020-08-28 14:49:54
digydia.com, www.digydia.com
2 entries


2650869449
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-03-31 13:55:16
2020-06-29 13:55:16
digydia.com, www.digydia.com
2 entries


2298936076
precert
CN=CloudFlare Inc RSA CA-1, O="CloudFlare, Inc.", L=San Francisco, C=US, ST=CA
2020-01-06 23:00:00
2020-10-14 10:00:00
www.digydia.com
1 entries


2349156397
leaf cert
CN=CloudFlare Inc ECC CA-2, O="CloudFlare, Inc.", L=San Francisco, C=US, ST=CA
2020-01-06 23:00:00
2020-10-09 10:00:00
www.digydia.com
1 entries


2173336416
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-11-26 16:14:08
2020-02-24 16:14:08
digydia.com, www.digydia.com
2 entries



11. Html-Content - Entries

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


12. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: dns105.ovh.net, ns105.ovh.net

QNr.DomainTypeNS used
1
net
NS
m.root-servers.net (2001:dc3::35)

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

Answer: dns10.ovh.net, dns11.ovh.net, dns12.ovh.net, dns13.ovh.net, dns15.ovh.net, ns10.ovh.net, ns11.ovh.net, ns12.ovh.net, ns13.ovh.net, ns15.ovh.net

Answer: dns10.ovh.net
2001:41d0:1:4a81::1, 213.251.188.129

Answer: dns11.ovh.net
2001:41d0:1:4a82::1, 213.251.188.130

Answer: dns12.ovh.net
2001:41d0:1:4a83::1, 213.251.188.131

Answer: dns15.ovh.net
2001:41d0:1:4a86::1, 213.251.188.134

Answer: ns10.ovh.net
2001:41d0:1:1981::1, 213.251.128.129

Answer: ns11.ovh.net
2001:41d0:1:1982::1, 213.251.128.130
3
ns105.ovh.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: dns10.ovh.net, dns11.ovh.net, dns12.ovh.net, dns13.ovh.net, dns15.ovh.net, ns10.ovh.net, ns11.ovh.net, ns12.ovh.net, ns13.ovh.net, ns15.ovh.net

Answer: dns10.ovh.net
2001:41d0:1:4a81::1, 213.251.188.129

Answer: dns11.ovh.net
2001:41d0:1:4a82::1, 213.251.188.130

Answer: dns12.ovh.net
2001:41d0:1:4a83::1, 213.251.188.131

Answer: dns15.ovh.net
2001:41d0:1:4a86::1, 213.251.188.134

Answer: ns10.ovh.net
2001:41d0:1:1981::1, 213.251.128.129

Answer: ns11.ovh.net
2001:41d0:1:1982::1, 213.251.128.130
4
dns13.ovh.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: dns10.ovh.net, dns11.ovh.net, dns12.ovh.net, dns13.ovh.net, dns15.ovh.net, ns10.ovh.net, ns11.ovh.net, ns12.ovh.net, ns13.ovh.net, ns15.ovh.net

Answer: dns10.ovh.net
2001:41d0:1:4a81::1, 213.251.188.129

Answer: dns11.ovh.net
2001:41d0:1:4a82::1, 213.251.188.130

Answer: dns12.ovh.net
2001:41d0:1:4a83::1, 213.251.188.131

Answer: dns15.ovh.net
2001:41d0:1:4a86::1, 213.251.188.134

Answer: ns10.ovh.net
2001:41d0:1:1981::1, 213.251.128.129

Answer: ns11.ovh.net
2001:41d0:1:1982::1, 213.251.128.130

Answer: ns12.ovh.net
2001:41d0:1:1983::1
5
ns13.ovh.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: dns10.ovh.net, dns11.ovh.net, dns12.ovh.net, dns13.ovh.net, dns15.ovh.net, ns10.ovh.net, ns11.ovh.net, ns12.ovh.net, ns13.ovh.net, ns15.ovh.net

Answer: dns10.ovh.net
2001:41d0:1:4a81::1, 213.251.188.129

Answer: dns11.ovh.net
2001:41d0:1:4a82::1, 213.251.188.130

Answer: dns12.ovh.net
2001:41d0:1:4a83::1, 213.251.188.131

Answer: dns15.ovh.net
2001:41d0:1:4a86::1, 213.251.188.134

Answer: ns10.ovh.net
2001:41d0:1:1981::1, 213.251.128.129

Answer: ns11.ovh.net
2001:41d0:1:1982::1, 213.251.128.130

Answer: ns12.ovh.net
2001:41d0:1:1983::1
6
ns15.ovh.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: dns10.ovh.net, dns11.ovh.net, dns12.ovh.net, dns13.ovh.net, dns15.ovh.net, ns10.ovh.net, ns11.ovh.net, ns12.ovh.net, ns13.ovh.net, ns15.ovh.net

Answer: dns10.ovh.net
2001:41d0:1:4a81::1, 213.251.188.129

Answer: dns11.ovh.net
2001:41d0:1:4a82::1, 213.251.188.130

Answer: dns12.ovh.net
2001:41d0:1:4a83::1, 213.251.188.131

Answer: dns15.ovh.net
2001:41d0:1:4a86::1, 213.251.188.134

Answer: ns10.ovh.net
2001:41d0:1:1981::1, 213.251.128.129

Answer: ns11.ovh.net
2001:41d0:1:1982::1, 213.251.128.130

Answer: ns12.ovh.net
2001:41d0:1:1983::1
7
dns13.ovh.net: 213.251.188.132
A
dns10.ovh.net (2001:41d0:1:4a81::1)
8
dns13.ovh.net: 2001:41d0:1:4a84::1
AAAA
dns10.ovh.net (2001:41d0:1:4a81::1)
9
ns13.ovh.net: 213.251.128.132
A
dns10.ovh.net (2001:41d0:1:4a81::1)
10
ns13.ovh.net: 2001:41d0:1:1984::1
AAAA
dns10.ovh.net (2001:41d0:1:4a81::1)
11
ns15.ovh.net: 213.251.128.134
A
dns10.ovh.net (2001:41d0:1:4a81::1)
12
ns15.ovh.net: 2001:41d0:1:1986::1
AAAA
dns10.ovh.net (2001:41d0:1:4a81::1)
13
dns105.ovh.net: 213.251.188.149
A
dns10.ovh.net (2001:41d0:1:4a81::1)
14
dns105.ovh.net: 2001:41d0:1:4a95::1
AAAA
dns10.ovh.net (2001:41d0:1:4a81::1)
15
ns105.ovh.net: 213.251.128.149
A
dns10.ovh.net (2001:41d0:1:4a81::1)
16
ns105.ovh.net: 2001:41d0:1:1995::1
AAAA
dns10.ovh.net (2001:41d0:1:4a81::1)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.digydia.com
0

no CAA entry found
1
0
digydia.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
digydia.com
1|www.digydia.com
ok
1
0
digydia.com
v=spf1 include:mx.ovh.com ~all
ok
1
0
www.digydia.com
3|welcome
ok
1
0
www.digydia.com
l|fr
ok
1
0
_acme-challenge.digydia.com

Name Error - The domain name does not exist
1
0
_acme-challenge.www.digydia.com

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

Name Error - The domain name does not exist
1
0
_acme-challenge.www.digydia.com.digydia.com

Name Error - The domain name does not exist
1
0
_acme-challenge.www.digydia.com.www.digydia.com

Name Error - The domain name does not exist
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=8e76f485-3a30-4a93-b275-1606ed196de9


Last Result: https://check-your-website.server-daten.de/?q=digydia.com - 2021-02-23 11:50:48


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

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