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


Info: Problems with 3.048.289 Letsencrypt certificates (378.325 accounts). They must be revoked (revocation starts 2020-03-04 20:00 UTC) - see Revoking certain certificates on March 4. Update 2020-03-07: Good news: Mass-revocation is canceled.

This tool: A check (SerialNumber) is added. Letsencrypt has published a list of critical SerialNumbers, this list is checked. See the part "9. Certificates". If there is a warning, renew that certificate and replace the current certificate.





1. IP-Addresses

HostTIP-Addressis auth.∑ Queries∑ Timeout
apollo.0x42.fi

Name Error
yes
1
0
www.apollo.0x42.fi

Name Error
yes
1
0


2. DNSSEC

Zone (*)DNSSEC - Informations (beta)

Zone: (root)
(root)
1 DS RR published



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 22545, Flags 256



1 RRSIG RR to validate DNSKEY RR found



Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 01.12.2019, 00:00:00, Signature-Inception: 10.11.2019, 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: fi
fi
1 DS RR in the parent zone found



1 RRSIG RR to validate DS RR found



Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 23.11.2019, 05:00:00, Signature-Inception: 10.11.2019, 04:00:00, KeyTag 22545, Signer-Name: (root)



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



3 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 42456, Flags 256



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



Public Key with Algorithm 8, KeyTag 54903, Flags 256



1 RRSIG RR to validate DNSKEY RR found



Algorithm: 8, 1 Labels, original TTL: 900 sec, Signature-expiration: 22.11.2019, 21:19:07, Signature-Inception: 09.11.2019, 06:26:09, KeyTag 44855, Signer-Name: fi



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



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

Zone: 0x42.fi
0x42.fi
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed domain name between the hashed NSEC3-owner and the hashed NextOwner. So the parent zone confirmes the non-existence of a DS RR.Bitmap: NS, DS, RRSIG



0 DNSKEY RR found





Zone: apollo.0x42.fi
apollo.0x42.fi
0 DS RR in the parent zone found

Zone: www.apollo.0x42.fi
www.apollo.0x42.fi
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.apollo.0x42.fi
  jerome.ns.cloudflare.com

apollo.0x42.fi
  jerome.ns.cloudflare.com

0x42.fi
  jerome.ns.cloudflare.com / 67m19


  lady.ns.cloudflare.com / 67m28

fi
  a.fi


  b.fi / s2.amx


  c.fi / ns-1.fi.de8.bind


  d.fi / s2.stu


  e.fi


  f.fi


  g.fi / 2.ber.pch


  h.fi


  i.fi / hivecast-1-defra.as15135.net FI-I


4. SOA-Entries


Domain:fi
Primary:a.fi
Mail:fi-domain-tech.ficora.fi
Serial:2019111052
Refresh:3605
Retry:1800
Expire:2419200
TTL:86400
num Entries:9


Domain:0x42.fi
Primary:jerome.ns.cloudflare.com
Mail:dns.cloudflare.com
Serial:2031642576
Refresh:10000
Retry:2400
Expire:604800
TTL:3600
num Entries:2


5. Screenshots (Beta)

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

6. Url-Checks

Domainname Http-StatusredirectSec.G







7. Comments

Aname "apollo.0x42.fi" is subdomain, public suffix is "fi", top-level-domain-type is "country-code", Country is Finland, tld-manager is "Finnish Transport and Communications Agency Traficom"
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.
AGood: Nameserver supports TCP connections: 2 good Nameserver
AGood: Nameserver supports Echo Capitalization: 2 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver
Nameserver doesn't pass all EDNS-Checks: i.fi: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found (hivecast-1-defra.as15135.net FI-I). COOKIE: fatal timeout. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: jerome.ns.cloudflare.com: 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.
Nameserver doesn't pass all EDNS-Checks: jerome.ns.cloudflare.com: 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.
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: 28090 milliseconds, 28.090 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=CloudFlare Inc ECC CA-2, O="CloudFlare, Inc.", L=San Francisco, C=US, ST=CA
0
1
2

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
1287291714
precert
CN=CloudFlare Inc ECC CA-2, O="CloudFlare, Inc.", L=San Francisco, C=US, ST=CA
2019-12-05 00:00:00
2020-10-09 12:00:00
*.0x42.fi, 0x42.fi, sni.cloudflaressl.com - 3 entries


700541697
precert
CN=CloudFlare Inc ECC CA-2, O="CloudFlare, Inc.", L=San Francisco, C=US, ST=CA
2019-01-05 00:00:00
2020-01-05 12:00:00
*.0x42.fi, 0x42.fi, sni.cloudflaressl.com - 3 entries



2. Source crt.sh - old and new certificates, sometimes very slow (Update 2020-01-11: Should now work again - code updated. Old message: currently no newer certificates - read Crt.sh has stopped - Letsencrypt-forum - may work next week again - 2019-12-02 - but I must check the code).

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

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
2164033917
precert
CN=CloudFlare Inc ECC CA-2, O="CloudFlare, Inc.", L=San Francisco, C=US, ST=CA
2019-12-04 23:00:00
2020-10-09 10:00:00
*.0x42.fi, 0x42.fi, sni.cloudflaressl.com
3 entries


1090538760
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-01-07 19:51:24
2019-04-07 18:51:24
apollo.0x42.fi
1 entries


1083002083
precert
CN=CloudFlare Inc ECC CA-2, O="CloudFlare, Inc.", L=San Francisco, C=US, ST=CA
2019-01-04 23:00:00
2020-01-05 11:00:00
*.0x42.fi, 0x42.fi, sni.cloudflaressl.com
3 entries



11. Html-Content - Entries

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


12. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
0x42.fi
0

no CAA entry found
1
0
fi
0

no CAA entry found
1
0


13. TXT - Entries

No TXT entries found


14. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=726bfd95-e4c0-4680-a96e-4904fb04881a


Last Result: https://check-your-website.server-daten.de/?q=apollo.0x42.fi - 2019-11-10 16:19:07


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

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