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



Y

Private IP-Address found

Checked:
21.07.2021 19:07:59


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
bitcode.codes
A
172.16.23.41
No Hostname found
yes
1
0

AAAA

yes


www.bitcode.codes
A
172.16.23.41
No Hostname found
yes
1
0

AAAA

yes


*.bitcode.codes
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 26838, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 11.08.2021, 00:00:00 +, Signature-Inception: 21.07.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: codes
codes
3 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 50164, DigestType 1 and Digest jtx9psydmomDZcgzy1NTIf0Cf/I=



DS with Algorithm 8, KeyTag 50164, DigestType 2 and Digest Juv4Ar/+UsG9i75QBFdZIb5JxoIY/+u30/gwdQqB2Tc=



DS with Algorithm 8, KeyTag 60022, DigestType 2 and Digest ggLOKfwFw9GKTitkSB+eFNkA0hD4a5tiJqs+8KyjZNc=



1 RRSIG RR to validate DS RR found



RRSIG-Owner codes., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 03.08.2021, 14:00:00 +, Signature-Inception: 21.07.2021, 13:00:00 +, KeyTag 26838, Signer-Name: (root)



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



4 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 37233, Flags 256



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



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



Public Key with Algorithm 8, KeyTag 61233, Flags 256



2 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner codes., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 19.08.2021, 10:22:20 +, Signature-Inception: 20.07.2021, 10:00:13 +, KeyTag 37233, Signer-Name: codes



RRSIG-Owner codes., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 19.08.2021, 10:22:20 +, Signature-Inception: 20.07.2021, 10:00:13 +, KeyTag 50164, Signer-Name: codes



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



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



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 50164, DigestType 1 and Digest "jtx9psydmomDZcgzy1NTIf0Cf/I=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone



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

Zone: bitcode.codes
bitcode.codes
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 "37dtgph5lh10ginp0teke6thhjgrp7ah" between the hashed NSEC3-owner "3784g1j76f34bd4069c7aejkgfvbeppe" and the hashed NextOwner "37mbb3ellscl9bujqguhutpahatc1kaf". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 3784g1j76f34bd4069c7aejkgfvbeppe.codes., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 19.08.2021, 12:14:00 +, Signature-Inception: 20.07.2021, 11:14:28 +, KeyTag 37233, Signer-Name: codes



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "k83doumrps7ihomk54eb9kq349gcbtc9" as Owner. That's the Hash of "codes" with the NextHashedOwnerName "k884kts6aog136hmb1qqilptdm50f0qq". So that domain name is the Closest Encloser of "bitcode.codes". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner k83doumrps7ihomk54eb9kq349gcbtc9.codes., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 19.08.2021, 11:39:56 +, Signature-Inception: 20.07.2021, 10:43:31 +, KeyTag 37233, Signer-Name: codes



2 DNSKEY RR found



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



Public Key with Algorithm 13, KeyTag 34505, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner bitcode.codes., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 18.08.2021, 21:21:04 +, Signature-Inception: 19.06.2021, 21:21:04 +, KeyTag 2371, Signer-Name: bitcode.codes



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



Error: DNSKEY 2371 signs DNSKEY RRset, but no confirming DS RR in the parent zone found. No chain of trust created.



RRSIG Type 1 validates the A - Result: 172.16.23.41
Validated: RRSIG-Owner bitcode.codes., Algorithm: 13, 2 Labels, original TTL: 300 sec, Signature-expiration: 22.07.2021, 18:08:07 +, Signature-Inception: 20.07.2021, 16:08:07 +, KeyTag 34505, Signer-Name: bitcode.codes



RRSIG Type 257 validates the CAA - Result: 5|issuecomodoca.com 5|issuedigicert.com 5|issuedigicert.com; cansignhttpexchanges=yes 5|issueletsencrypt.org 9|issuewildcomodoca.com 9|issuewilddigicert.com 9|issuewilddigicert.com; cansignhttpexchanges=yes 9|issuewildletsencrypt.org
Validated: RRSIG-Owner bitcode.codes., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 22.07.2021, 18:08:08 +, Signature-Inception: 20.07.2021, 16:08:08 +, KeyTag 34505, Signer-Name: bitcode.codes



CNAME-Query sends a valid NSEC RR as result with the query name "bitcode.codes" equal the NSEC-owner "bitcode.codes" and the NextOwner "\000.bitcode.codes". So the zone confirmes the not-existence of that CNAME RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, NS, SOA, 13, MX, TXT, AAAA, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, DNSKEY, TLSA, 53, HIP, CDS, CDNSKEY, 61, 64, 65, 99, URI, CAA Validated: RRSIG-Owner bitcode.codes., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 22.07.2021, 18:08:08 +, Signature-Inception: 20.07.2021, 16:08:08 +, KeyTag 34505, Signer-Name: bitcode.codes



Status: Good. NoData-Proof required and found.



TXT-Query sends a valid NSEC RR as result with the query name "bitcode.codes" equal the NSEC-owner "bitcode.codes" and the NextOwner "\000.bitcode.codes". So the zone confirmes the not-existence of that TXT RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, NS, SOA, 13, MX, AAAA, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, DNSKEY, TLSA, 53, HIP, CDS, CDNSKEY, 61, 64, 65, 99, URI, CAA Validated: RRSIG-Owner bitcode.codes., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 22.07.2021, 18:08:08 +, Signature-Inception: 20.07.2021, 16:08:08 +, KeyTag 34505, Signer-Name: bitcode.codes



Status: Good. NoData-Proof required and found.



AAAA-Query sends a valid NSEC RR as result with the query name "bitcode.codes" equal the NSEC-owner "bitcode.codes" and the NextOwner "\000.bitcode.codes". So the zone confirmes the not-existence of that AAAA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, NS, SOA, 13, MX, TXT, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, DNSKEY, TLSA, 53, HIP, CDS, CDNSKEY, 61, 64, 65, 99, URI, CAA Validated: RRSIG-Owner bitcode.codes., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 22.07.2021, 18:08:08 +, Signature-Inception: 20.07.2021, 16:08:08 +, KeyTag 34505, Signer-Name: bitcode.codes



Status: Good. NoData-Proof required and found.



TLSA-Query (_443._tcp.bitcode.codes) sends a valid NSEC RR as result with the query name "_443._tcp.bitcode.codes" equal the NSEC-owner "_443._tcp.bitcode.codes" and the NextOwner "\000._443._tcp.bitcode.codes". So the zone confirmes the not-existence of that TLSA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: RRSIG, NSEC Validated: RRSIG-Owner _443._tcp.bitcode.codes., Algorithm: 13, 4 Labels, original TTL: 3600 sec, Signature-expiration: 22.07.2021, 18:08:07 +, Signature-Inception: 20.07.2021, 16:08:07 +, KeyTag 34505, Signer-Name: bitcode.codes



Status: Good. NoData-Proof required and found.

Zone: www.bitcode.codes
www.bitcode.codes
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "www.bitcode.codes" and the NextOwner "\000.www.bitcode.codes". So the parent zone confirmes the non-existence of a DS RR.
Bitmap: A, 13, MX, TXT, AAAA, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, TLSA, 53, HIP, 61, 64, 65, 99, URI, CAA



RRSIG Type 1 validates the A - Result: 172.16.23.41
Validated: RRSIG-Owner www.bitcode.codes., Algorithm: 13, 3 Labels, original TTL: 300 sec, Signature-expiration: 22.07.2021, 18:08:08 +, Signature-Inception: 20.07.2021, 16:08:08 +, KeyTag 34505, Signer-Name: bitcode.codes



CNAME-Query sends a valid NSEC RR as result with the query name "www.bitcode.codes" equal the NSEC-owner "www.bitcode.codes" and the NextOwner "\000.www.bitcode.codes". So the zone confirmes the not-existence of that CNAME RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, 13, MX, TXT, AAAA, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, TLSA, 53, HIP, 61, 64, 65, 99, URI, CAA Validated: RRSIG-Owner www.bitcode.codes., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 22.07.2021, 18:08:08 +, Signature-Inception: 20.07.2021, 16:08:08 +, KeyTag 34505, Signer-Name: bitcode.codes



Status: Good. NoData-Proof required and found.



TXT-Query sends a valid NSEC RR as result with the query name "www.bitcode.codes" equal the NSEC-owner "www.bitcode.codes" and the NextOwner "\000.www.bitcode.codes". So the zone confirmes the not-existence of that TXT RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, 13, MX, AAAA, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, TLSA, 53, HIP, 61, 64, 65, 99, URI, CAA Validated: RRSIG-Owner www.bitcode.codes., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 22.07.2021, 18:08:08 +, Signature-Inception: 20.07.2021, 16:08:08 +, KeyTag 34505, Signer-Name: bitcode.codes



Status: Good. NoData-Proof required and found.



AAAA-Query sends a valid NSEC RR as result with the query name "www.bitcode.codes" equal the NSEC-owner "www.bitcode.codes" and the NextOwner "\000.www.bitcode.codes". So the zone confirmes the not-existence of that AAAA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, 13, MX, TXT, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, TLSA, 53, HIP, 61, 64, 65, 99, URI, CAA Validated: RRSIG-Owner www.bitcode.codes., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 22.07.2021, 18:08:08 +, Signature-Inception: 20.07.2021, 16:08:08 +, KeyTag 34505, Signer-Name: bitcode.codes



Status: Good. NoData-Proof required and found.



TLSA-Query (_443._tcp.www.bitcode.codes) sends a valid NSEC RR as result with the query name "_443._tcp.www.bitcode.codes" equal the NSEC-owner "_443._tcp.www.bitcode.codes" and the NextOwner "\000._443._tcp.www.bitcode.codes". So the zone confirmes the not-existence of that TLSA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: RRSIG, NSEC Validated: RRSIG-Owner _443._tcp.www.bitcode.codes., Algorithm: 13, 5 Labels, original TTL: 3600 sec, Signature-expiration: 22.07.2021, 18:08:08 +, Signature-Inception: 20.07.2021, 16:08:08 +, KeyTag 34505, Signer-Name: bitcode.codes



Status: Good. NoData-Proof required and found.



CAA-Query sends a valid NSEC RR as result with the query name "www.bitcode.codes" equal the NSEC-owner "www.bitcode.codes" and the NextOwner "\000.www.bitcode.codes". So the zone confirmes the not-existence of that CAA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, 13, MX, TXT, AAAA, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, TLSA, 53, HIP, 61, 64, 65, 99, URI Validated: RRSIG-Owner www.bitcode.codes., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 22.07.2021, 18:08:08 +, Signature-Inception: 20.07.2021, 16:08:08 +, KeyTag 34505, Signer-Name: bitcode.codes



Status: Good. NoData-Proof required and found.


3. Name Servers

DomainNameserverNS-IP
www.bitcode.codes
  hal.ns.cloudflare.com / 67m34

bitcode.codes
  hal.ns.cloudflare.com / 67m35
108.162.193.174
Chicago/Illinois/United States (US) - Cloudflare, Inc.


 
172.64.33.174
Ashburn/Virginia/United States (US) - Cloudflare, Inc.


 
173.245.59.174
Chicago/Illinois/United States (US) - Cloudflare, Inc.


 
2606:4700:58::adf5:3bae
Montreal/Quebec/Canada (CA) - Cloudflare, Inc.


 
2803:f800:50::6ca2:c1ae
San José/Provincia de San Jose/Costa Rica (CR) - Cloudflare, Inc.


 
2a06:98c1:50::ac40:21ae
London/England/United Kingdom (GB) - CloudFLARENET-EU


  paityn.ns.cloudflare.com / 67m35
108.162.194.18
Chicago/Illinois/United States (US) - Cloudflare, Inc.


 
162.159.38.18
Chicago/Illinois/United States (US) - Cloudflare, Inc.


 
172.64.34.18
Ashburn/Virginia/United States (US) - Cloudflare, Inc.


 
2606:4700:50::a29f:2612
Montreal/Quebec/Canada (CA) - Cloudflare, Inc.


 
2803:f800:50::6ca2:c212
San José/Provincia de San Jose/Costa Rica (CR) - Cloudflare, Inc.


 
2a06:98c1:50::ac40:2212
London/England/United Kingdom (GB) - CloudFLARENET-EU

codes
  demand.alpha.aridns.net.au / dns2.frpar1


  demand.beta.aridns.net.au / dns1.defra1


  demand.delta.aridns.net.au / dns4.frpar1


  demand.gamma.aridns.net.au / dns1.defra1


4. SOA-Entries


Domain:codes
Zone-Name:codes
Primary:demand.alpha.aridns.net.au
Mail:hostmaster.donuts.co
Serial:1626886963
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:4


Domain:bitcode.codes
Zone-Name:bitcode.codes
Primary:hal.ns.cloudflare.com
Mail:dns.cloudflare.com
Serial:2037847312
Refresh:10000
Retry:2400
Expire:604800
TTL:3600
num Entries:12


Domain:www.bitcode.codes
Zone-Name:bitcode.codes
Primary:hal.ns.cloudflare.com
Mail:dns.cloudflare.com
Serial:2037847312
Refresh:10000
Retry:2400
Expire:604800
TTL:3600
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 "bitcode.codes" is domain, public suffix is ".codes", top-level-domain is ".codes", top-level-domain-type is "generic", tld-manager is "Binky Moon, LLC", num .codes-domains preloaded: 43 (complete: 151507)
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.
Ybitcode.codes

172.16.23.41
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: 172.16.0.0 to 172.31.255.255: Class B - 16 private net, every with 65.536 addresses
Ywww.bitcode.codes

172.16.23.41
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: 172.16.0.0 to 172.31.255.255: Class B - 16 private net, every with 65.536 addresses

2. 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, 7 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
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: hal.ns.cloudflare.com, paityn.ns.cloudflare.com, 2 Name Servers included in Delegation: hal.ns.cloudflare.com, paityn.ns.cloudflare.com, 2 Name Servers included in 1 Zone definitions: hal.ns.cloudflare.com, paityn.ns.cloudflare.com, 1 Name Servers listed in SOA.Primary: hal.ns.cloudflare.com.
AGood: Only one SOA.Primary Name Server found.: hal.ns.cloudflare.com.
AGood: SOA.Primary Name Server included in the delegation set.: hal.ns.cloudflare.com.
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: hal.ns.cloudflare.com, paityn.ns.cloudflare.com
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: 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: com
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: cloudflare.com
AGood: Name servers with different Country locations found: 2 Name Servers, 4 Countries: CA, CR, GB, US
AInfo: Ipv4-Subnet-list: 6 Name Servers, 4 different subnets (first Byte): 108., 162., 172., 173., 4 different subnets (first two Bytes): 108.162., 162.159., 172.64., 173.245., 6 different subnets (first three Bytes): 108.162.193., 108.162.194., 162.159.38., 172.64.33., 172.64.34., 173.245.59.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: IPv6-Subnet-list: 6 Name Servers with IPv6, 3 different subnets (first block): 2606:, 2803:, 2a06:, 3 different subnets (first two blocks): 2606:4700:, 2803:f800:, 2a06:98c1:, 4 different subnets (first three blocks): 2606:4700:0050:, 2606:4700:0058:, 2803:f800:0050:, 2a06:98c1:0050:, 4 different subnets (first four blocks): 2606:4700:0050:0000:, 2606:4700:0058:0000:, 2803:f800:0050:0000:, 2a06:98c1:0050:0000:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 12 good Nameserver
AGood: Nameserver supports Echo Capitalization: 12 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 12 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 12 good Nameserver
AGood: All SOA have the same Serial Number
Agood: CAA entries found, creating certificate is limited: comodoca.com is allowed to create certificates
Agood: CAA entries found, creating certificate is limited: digicert.com is allowed to create certificates
Agood: CAA entries found, creating certificate is limited: letsencrypt.org is allowed to create certificates
Agood: CAA entries found, creating certificate is limited: comodoca.com is allowed to create wildcard-certificates
Agood: CAA entries found, creating certificate is limited: digicert.com is allowed to create wildcard-certificates
Agood: CAA entries found, creating certificate is limited: letsencrypt.org is allowed to create wildcard-certificates

3. 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: 36944 milliseconds, 36.944 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=Encryption Everywhere DV TLS CA - G1, OU=www.digicert.com, O=DigiCert Inc, C=US
0
2
2
CN=Cloudflare Inc ECC CA-3, O="Cloudflare, Inc.", C=US
0
2
2
CN=R3, O=Let's Encrypt, C=US
0
2
2

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
2741028200
precert
CN=Cloudflare Inc ECC CA-3, O="Cloudflare, Inc.", C=US
2021-07-20 00:00:00
2021-10-17 23:59:59
*.bitcode.codes, bitcode.codes - 2 entries


2738198047
precert
CN=Cloudflare Inc ECC CA-3, O="Cloudflare, Inc.", C=US
2021-07-19 00:00:00
2022-07-18 23:59:59
*.bitcode.codes, bitcode.codes, sni.cloudflaressl.com - 3 entries


2669205467
leaf cert
CN=R3, O=Let's Encrypt, C=US
2021-06-27 18:38:26
2021-09-25 18:38:25
bitcode.codes, www.bitcode.codes - 2 entries


2669047502
leaf cert
CN=R3, O=Let's Encrypt, C=US
2021-06-27 17:04:01
2021-09-25 17:04:00
www.bitcode.codes - 1 entries


2668022902
precert
CN=Encryption Everywhere DV TLS CA - G1, OU=www.digicert.com, O=DigiCert Inc, C=US
2021-06-27 00:00:00
2022-06-27 23:59:59
www.bitcode.codes - 1 entries


2668023027
precert
CN=Encryption Everywhere DV TLS CA - G1, OU=www.digicert.com, O=DigiCert Inc, C=US
2021-06-27 00:00:00
2022-06-27 23:59:59
*.bitcode.codes, bitcode.codes - 2 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
2
2
CN=Encryption Everywhere DV TLS CA - G1, OU=www.digicert.com, O=DigiCert Inc, C=US
0
2
2
CN=Cloudflare Inc ECC CA-3, O="Cloudflare, Inc.", C=US
0
2
2

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
4899897644
precert
CN=Cloudflare Inc ECC CA-3, O="Cloudflare, Inc.", C=US
2021-07-19 22:00:00
2021-10-17 21:59:59
*.bitcode.codes, bitcode.codes
2 entries


4894142017
precert
CN=Cloudflare Inc ECC CA-3, O="Cloudflare, Inc.", C=US
2021-07-18 22:00:00
2022-07-18 21:59:59
*.bitcode.codes, bitcode.codes, sni.cloudflaressl.com
3 entries


4771482664
leaf cert
CN=R3, O=Let's Encrypt, C=US
2021-06-27 16:38:26
2021-09-25 16:38:25
bitcode.codes, www.bitcode.codes
2 entries


4771181575
leaf cert
CN=R3, O=Let's Encrypt, C=US
2021-06-27 15:04:01
2021-09-25 15:04:00
www.bitcode.codes
1 entries


4769432140
precert
CN=Encryption Everywhere DV TLS CA - G1, OU=www.digicert.com, O=DigiCert Inc, C=US
2021-06-26 22:00:00
2022-06-27 21:59:59
*.bitcode.codes, bitcode.codes
2 entries


4769431737
precert
CN=Encryption Everywhere DV TLS CA - G1, OU=www.digicert.com, O=DigiCert Inc, C=US
2021-06-26 22:00:00
2022-06-27 21:59:59
www.bitcode.codes
1 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: hal.ns.cloudflare.com, paityn.ns.cloudflare.com

QNr.DomainTypeNS used
1
com
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
hal.ns.cloudflare.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns3.cloudflare.com, ns4.cloudflare.com, ns5.cloudflare.com, ns6.cloudflare.com, ns7.cloudflare.com

Answer: ns3.cloudflare.com
162.159.0.33, 162.159.7.226, 2400:cb00:2049:1::a29f:21, 2400:cb00:2049:1::a29f:7e2

Answer: ns4.cloudflare.com
162.159.1.33, 162.159.8.55, 2400:cb00:2049:1::a29f:121, 2400:cb00:2049:1::a29f:837

Answer: ns5.cloudflare.com
162.159.2.9, 162.159.9.55, 2400:cb00:2049:1::a29f:209, 2400:cb00:2049:1::a29f:937

Answer: ns6.cloudflare.com
162.159.3.11, 162.159.5.6, 2400:cb00:2049:1::a29f:30b, 2400:cb00:2049:1::a29f:506

Answer: ns7.cloudflare.com
162.159.4.8
3
paityn.ns.cloudflare.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns3.cloudflare.com, ns4.cloudflare.com, ns5.cloudflare.com, ns6.cloudflare.com, ns7.cloudflare.com

Answer: ns3.cloudflare.com
162.159.0.33, 162.159.7.226, 2400:cb00:2049:1::a29f:21, 2400:cb00:2049:1::a29f:7e2

Answer: ns4.cloudflare.com
162.159.1.33, 162.159.8.55, 2400:cb00:2049:1::a29f:121, 2400:cb00:2049:1::a29f:837

Answer: ns5.cloudflare.com
162.159.2.9, 162.159.9.55, 2400:cb00:2049:1::a29f:209, 2400:cb00:2049:1::a29f:937

Answer: ns6.cloudflare.com
162.159.3.11, 162.159.5.6, 2400:cb00:2049:1::a29f:30b, 2400:cb00:2049:1::a29f:506

Answer: ns7.cloudflare.com
162.159.4.8
4
hal.ns.cloudflare.com: 108.162.193.174, 172.64.33.174, 173.245.59.174
A
ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)
5
hal.ns.cloudflare.com: 2606:4700:58::adf5:3bae, 2803:f800:50::6ca2:c1ae, 2a06:98c1:50::ac40:21ae
AAAA
ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)
6
paityn.ns.cloudflare.com: 108.162.194.18, 162.159.38.18, 172.64.34.18
A
ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)
7
paityn.ns.cloudflare.com: 2606:4700:50::a29f:2612, 2803:f800:50::6ca2:c212, 2a06:98c1:50::ac40:2212
AAAA
ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.bitcode.codes
0

no CAA entry found
1
0
bitcode.codes
5
issue
comodoca.com
1
0

9
issuewild
comodoca.com
1
0

5
issue
digicert.com
1
0

9
issuewild
digicert.com
1
0

5
issue
digicert.com; cansignhttpexchanges=yes
1
0

9
issuewild
digicert.com; cansignhttpexchanges=yes
1
0

5
issue
letsencrypt.org
1
0

9
issuewild
letsencrypt.org
1
0
codes
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
bitcode.codes

ok
1
0
www.bitcode.codes

ok
1
0
_acme-challenge.bitcode.codes

Name Error - The domain name does not exist
1
0
_acme-challenge.www.bitcode.codes

Name Error - The domain name does not exist
1
0
_acme-challenge.bitcode.codes.bitcode.codes

Name Error - The domain name does not exist
1
0
_acme-challenge.www.bitcode.codes.bitcode.codes

Name Error - The domain name does not exist
1
0
_acme-challenge.www.bitcode.codes.www.bitcode.codes

Name Error - The domain name does not exist
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=6c489878-4c26-4664-89b8-73d54d88e29b


Last Result: https://check-your-website.server-daten.de/?q=bitcode.codes - 2021-07-21 19:07:59


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

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