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

hide

skip EDNS-Check

skip Content-Check

check links

No dns entry found - perhaps mistype. Or wrong IDN

Checked:
29.12.2020 01:57:25

Older results

W - 23.10.2020 02:47:21

W - 16.09.2020 20:55:24

W - 27.07.2020 14:19:14

W - 30.01.2020 21:18:05

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
bmteck.org		Name Error	yes	1	0
www.bmteck.org		Name Error	yes	1	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 26116, Flags 256


	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: 10.01.2021, 00:00:00 +, Signature-Inception: 20.12.2020, 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: org
org	1 DS RR in the parent zone found


	DS with Algorithm 8, KeyTag 26974, DigestType 2 and Digest T+3ilMU/Q4oVjEHTlInNeKhr6w2KCur/FHRcDRbh3jI=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner org., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 10.01.2021, 17:00:00 +, Signature-Inception: 28.12.2020, 16:00:00 +, KeyTag 26116, Signer-Name: (root)


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


	3 DNSKEY RR found


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


	Public Key with Algorithm 8, KeyTag 34266, Flags 256


	Public Key with Algorithm 8, KeyTag 63858, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner org., Algorithm: 8, 1 Labels, original TTL: 900 sec, Signature-expiration: 18.01.2021, 15:27:59 +, Signature-Inception: 28.12.2020, 14:27:59 +, KeyTag 26974, Signer-Name: org


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


	• Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 26974, DigestType 2 and Digest "T+3ilMU/Q4oVjEHTlInNeKhr6w2KCur/FHRcDRbh3jI=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: bmteck.org
bmteck.org	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 "0dm3eh5fffi4sh1mpooqdrq01fffgd22" between the hashed NSEC3-owner "0dlul926f4cu2n5kl1e6o8d1vrptoinb" and the hashed NextOwner "0dm8o30bee15mb1kcogon7k55ebet8i2". So the parent zone confirmes the not-existence of a DS RR. Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 0dlul926f4cu2n5kl1e6o8d1vrptoinb.org., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 18.01.2021, 15:27:59 +, Signature-Inception: 28.12.2020, 14:27:59 +, KeyTag 63858, Signer-Name: org


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "d6n22mffurrkkhup4jscmntse266m0lq" as Owner. That's the Hash of "org" with the NextHashedOwnerName "d6n6gr81bv9d3ce1vsg6fn5bau7ub671". So that domain name is the Closest Encloser of "bmteck.org". Opt-Out: True. Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner d6n22mffurrkkhup4jscmntse266m0lq.org., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 19.01.2021, 00:57:00 +, Signature-Inception: 28.12.2020, 23:57:00 +, KeyTag 63858, Signer-Name: org


	The ClosestEncloser says, that "*.org" with the Hash "nrkvoje3pqhcjsfelcggagr5kiqbrapr" is a possible Wildcard of the DS Query Name. But the DS-Query in the parent zone sends a valid NSEC3 RR With the owner "nrkvn0ljdqacnn3kc5q1aek73ra7cldm" and the Next Owner "nrl0r32a5ts4gk50tgn8fm7doj8v52ba", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: True Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner nrkvn0ljdqacnn3kc5q1aek73ra7cldm.org., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 18.01.2021, 15:27:59 +, Signature-Inception: 28.12.2020, 14:27:59 +, KeyTag 63858, Signer-Name: org

Zone: www.bmteck.org
www.bmteck.org	0 DS RR in the parent zone found


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "d6n22mffurrkkhup4jscmntse266m0lq" as Owner. That's the Hash of "org" with the NextHashedOwnerName "d6n6gr81bv9d3ce1vsg6fn5bau7ub671". So that domain name is the Closest Encloser of "www.bmteck.org". Opt-Out: True. Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner d6n22mffurrkkhup4jscmntse266m0lq.org., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 19.01.2021, 00:57:00 +, Signature-Inception: 28.12.2020, 23:57:00 +, KeyTag 63858, Signer-Name: org


	The ClosestEncloser says, that "*.org" with the Hash "nrkvoje3pqhcjsfelcggagr5kiqbrapr" is a possible Wildcard of the DS Query Name. But the DS-Query in the parent zone sends a valid NSEC3 RR With the owner "nrkvn0ljdqacnn3kc5q1aek73ra7cldm" and the Next Owner "nrl0r32a5ts4gk50tgn8fm7doj8v52ba", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: True Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner nrkvn0ljdqacnn3kc5q1aek73ra7cldm.org., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 18.01.2021, 15:27:59 +, Signature-Inception: 28.12.2020, 14:27:59 +, KeyTag 63858, Signer-Name: org

3. Name Servers

Domain	Nameserver
www.bmteck.org	• a0.org.afilias-nst.info
bmteck.org	• a0.org.afilias-nst.info
org	• a0.org.afilias-nst.info / ns000b.app10.ams2.afilias-nst.info	•
	• a2.org.afilias-nst.info / LHR3	•
	• b0.org.afilias-nst.org / ns000b.app26.ams2.afilias-nst.info	•
	• b2.org.afilias-nst.org / LHR3	•
	• c0.org.afilias-nst.info / app23.iad1.hosts.meta.redstone.afilias-nst.info-2020121101	•
	• d0.org.afilias-nst.org / ns000b.app7.ams2.afilias-nst.info	•

4. SOA-Entries

Domain:	org
Zone-Name:	org
Primary:	a0.org.afilias-nst.info
Mail:	noc.afilias-nst.info
Serial:	2014198112
Refresh:	1800
Retry:	900
Expire:	604800
TTL:	86400
num Entries:	6

Domain:	bmteck.org
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:	1

Domain:	www.bmteck.org
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

Domainname	Http-Status	redirect	Sec.	G
•

7. Comments

	1. General Results, most used to calculate the result
A	name "bmteck.org" is domain, public suffix is ".org", top-level-domain is ".org", top-level-domain-type is "generic", tld-manager is "Public Interest Registry (PIR)", num .org-domains preloaded: 4748 (complete: 131120)
A	good: No asked Authoritative Name Server had a timeout
A	DNS: "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.
	2. DNS- and NameServer - Checks
A
A
A	Info:: 6 different Name Servers found: a0.org.afilias-nst.info, a2.org.afilias-nst.info, b0.org.afilias-nst.org, b2.org.afilias-nst.org, c0.org.afilias-nst.info, d0.org.afilias-nst.org, 6 Name Servers included in Delegation: a0.org.afilias-nst.info, a2.org.afilias-nst.info, b0.org.afilias-nst.org, b2.org.afilias-nst.org, c0.org.afilias-nst.info, d0.org.afilias-nst.org, 6 Name Servers included in 1 Zone definitions: a0.org.afilias-nst.info, a2.org.afilias-nst.info, b0.org.afilias-nst.org, b2.org.afilias-nst.org, c0.org.afilias-nst.info, d0.org.afilias-nst.org, 1 Name Servers listed in SOA.Primary: a0.org.afilias-nst.info.
A	Good: Only one SOA.Primary Name Server found.: a0.org.afilias-nst.info.
A	Good: SOA.Primary Name Server included in the delegation set.: a0.org.afilias-nst.info.
A	Good: All Name Server Domain Names have a Public Suffix.
A
A	Good: Nameserver supports TCP connections: 6 good Nameserver
A	Good: Nameserver supports Echo Capitalization: 6 good Nameserver
A	Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 6 good Nameserver
	Nameserver doesn't pass all EDNS-Checks: a0.org.afilias-nst.info: 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: a0.org.afilias-nst.info: 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.
A	Good: 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
	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.
A	Good: 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
A	Duration: 29983 milliseconds, 29.983 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)

Issuer				last 7 days	active	num Certs
CN=GTS CA 1D2, O=Google Trust Services, C=US				0	1	4

CertSpotter-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
2068830927 leaf cert	CN=GTS CA 1D2, O=Google Trust Services, C=US	2020-11-15 04:25:28	2021-02-13 04:25:28	www.bmteck.org - 1 entries
1783252851 leaf cert	CN=GTS CA 1D2, O=Google Trust Services, C=US	2020-07-20 21:10:46	2020-10-18 21:10:46	www.bmteck.org - 1 entries
1393418693 precert	CN=GTS CA 1D2, O=Google Trust Services, C=US	2020-01-28 03:07:19	2020-04-27 03:07:19	www.bmteck.org - 1 entries
1393290635 precert	CN=GTS CA 1D2, O=Google Trust Services, C=US	2020-01-28 01:31:21	2020-04-27 01:31:21	www.bmteck.org - 1 entries

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

Issuer				last 7 days	active	num Certs
CN=GTS CA 1D2, O=Google Trust Services, C=US				0	1	7

CRT-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
3670329502 leaf cert	CN=GTS CA 1D2, O=Google Trust Services, C=US	2020-11-15 03:25:28	2021-02-13 03:25:28	www.bmteck.org 1 entries
3403792384 leaf cert	CN=GTS CA 1D2, O=Google Trust Services, C=US	2020-09-17 01:12:07	2020-12-16 02:12:07	www.bmteck.org 1 entries
3148582205 leaf cert	CN=GTS CA 1D2, O=Google Trust Services, C=US	2020-07-20 19:10:46	2020-10-18 19:10:46	www.bmteck.org 1 entries
2904897091 leaf cert	CN=GTS CA 1D2, O=Google Trust Services, C=US	2020-05-23 13:09:34	2020-08-21 13:09:34	www.bmteck.org 1 entries
2640713130 leaf cert	CN=GTS CA 1D2, O=Google Trust Services, C=US	2020-03-26 08:08:22	2020-06-24 07:08:22	www.bmteck.org 1 entries
2404075726 leaf cert	CN=GTS CA 1D2, O=Google Trust Services, C=US	2020-01-28 02:07:19	2020-04-27 01:07:19	www.bmteck.org 1 entries
2385606760 precert	CN=GTS CA 1D2, O=Google Trust Services, C=US	2020-01-28 00:31:21	2020-04-26 23:31:21	www.bmteck.org 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:

No NameServer - IP address - Informations found

13. CAA - Entries

Domainname	flag	Name	Value	∑ Queries	∑ Timeout
org	0		no CAA entry found	1	0

14. TXT - Entries

No TXT entries found

15. Portchecks

No Port checks

Permalink: https://check-your-website.server-daten.de/?i=ab7c259f-7c99-4057-8b43-0bb5e8344d65

Last Result: https://check-your-website.server-daten.de/?q=bmteck.org - 2020-12-29 01:57:25

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

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