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

...

skip EDNS-Check

skip Content-Check

check links

DNS-problem - authoritative Nameserver refused, not defined or timeout

Checked:
23.11.2023 16:56:53

Older results

X - 20.11.2023 18:18:13

X - 20.11.2023 16:24:16

X - 16.11.2023 20:36:06

X - 15.11.2023 11:52:09

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
synpromics.com	A		yes	2	0
	AAAA		yes
www.synpromics.com	CNAME	synpromics.com	yes	1	0
*.synpromics.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 46780, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 11.12.2023, 00:00:00 +, Signature-Inception: 20.11.2023, 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: 06.12.2023, 05:00:00 +, Signature-Inception: 23.11.2023, 04:00:00 +, KeyTag 46780, Signer-Name: (root)


	• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 46780 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 63246, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 01.12.2023, 17:24:21 +, Signature-Inception: 16.11.2023, 17: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: synpromics.com
synpromics.com	2 DS RR in the parent zone found


	DS with Algorithm 13, KeyTag 7604, DigestType 2 and Digest PLZL126jVRtVmyI1Z4HiZ++yaB9KCNBgEVnuIsiJ7Dk=


	DS with Algorithm 13, KeyTag 14793, DigestType 2 and Digest 2W4l6C6HBFQhA5j5jgDPucZylZytk/fkJZHfHdBAeGI=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner synpromics.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 30.11.2023, 08:04:09 +, Signature-Inception: 23.11.2023, 06:54:09 +, KeyTag 63246, Signer-Name: com


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


	2 DNSKEY RR found


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


	Public Key with Algorithm 13, KeyTag 14694, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner synpromics.com., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 08.12.2023, 15:56:30 +, Signature-Inception: 23.11.2023, 15:56:30 +, KeyTag 7604, Signer-Name: synpromics.com


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


	• Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 7604, DigestType 2 and Digest "PLZL126jVRtVmyI1Z4HiZ++yaB9KCNBgEVnuIsiJ7Dk=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone


	A-Query sends a valid NSEC RR as result with the query name "synpromics.com" equal the NSEC-owner "synpromics.com" and the NextOwner "_acme-challenge.synpromics.com". So the zone confirmes the not-existence of that A RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: NS, SOA, RRSIG, NSEC, DNSKEY, CDS, CDNSKEY Validated: RRSIG-Owner synpromics.com., Algorithm: 13, 2 Labels, original TTL: 600 sec, Signature-expiration: 08.12.2023, 15:56:30 +, Signature-Inception: 23.11.2023, 15:56:30 +, KeyTag 14694, Signer-Name: synpromics.com


	Status: Good. NoData-Proof required and found.


	CNAME-Query sends a valid NSEC RR as result with the query name "synpromics.com" equal the NSEC-owner "synpromics.com" and the NextOwner "_acme-challenge.synpromics.com". 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: NS, SOA, RRSIG, NSEC, DNSKEY, CDS, CDNSKEY Validated: RRSIG-Owner synpromics.com., Algorithm: 13, 2 Labels, original TTL: 600 sec, Signature-expiration: 08.12.2023, 15:56:30 +, Signature-Inception: 23.11.2023, 15:56:30 +, KeyTag 14694, Signer-Name: synpromics.com


	Status: Good. NoData-Proof required and found.


	TXT-Query sends a valid NSEC RR as result with the query name "synpromics.com" equal the NSEC-owner "synpromics.com" and the NextOwner "_acme-challenge.synpromics.com". 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: NS, SOA, RRSIG, NSEC, DNSKEY, CDS, CDNSKEY Validated: RRSIG-Owner synpromics.com., Algorithm: 13, 2 Labels, original TTL: 600 sec, Signature-expiration: 08.12.2023, 15:56:30 +, Signature-Inception: 23.11.2023, 15:56:30 +, KeyTag 14694, Signer-Name: synpromics.com


	Status: Good. NoData-Proof required and found.


	AAAA-Query sends a valid NSEC RR as result with the query name "synpromics.com" equal the NSEC-owner "synpromics.com" and the NextOwner "_acme-challenge.synpromics.com". 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: NS, SOA, RRSIG, NSEC, DNSKEY, CDS, CDNSKEY Validated: RRSIG-Owner synpromics.com., Algorithm: 13, 2 Labels, original TTL: 600 sec, Signature-expiration: 08.12.2023, 15:56:30 +, Signature-Inception: 23.11.2023, 15:56:30 +, KeyTag 14694, Signer-Name: synpromics.com


	Status: Good. NoData-Proof required and found.


	TLSA-Query (_443._tcp.synpromics.com) sends a valid NSEC RR as result with the owner name synpromics.com. So that's the Closest Encloser of the query name. TLSA-Query sends a valid NSEC RR as result and covers the Wildcard expansion of the ClosestEncloser with the owner "synpromics.com" and the NextOwner "_acme-challenge.synpromics.com". So that NSEC confirms the not-existence of the Wildcard expansion. Bitmap: NS, SOA, RRSIG, NSEC, DNSKEY, CDS, CDNSKEY Validated: RRSIG-Owner synpromics.com., Algorithm: 13, 2 Labels, original TTL: 600 sec, Signature-expiration: 08.12.2023, 15:56:30 +, Signature-Inception: 23.11.2023, 15:56:30 +, KeyTag 14694, Signer-Name: synpromics.com


	Status: Good. NXDomain-Proof required and found.


	TLSA-Query (_443._tcp.synpromics.com) sends a valid NSEC RR as result with the query name "_443._tcp.synpromics.com" between the NSEC-owner "_domainconnect.synpromics.com" and the NextOwner "_acme-challenge.gitlab.synpromics.com". So the zone confirmes the not-existence of that TLSA RR.TLSA-Query (_443._tcp.synpromics.com) sends a valid NSEC RR as result with the parent Wildcard "*._tcp.synpromics.com" between the NSEC-owner "_domainconnect.synpromics.com" and the NextOwner "_acme-challenge.gitlab.synpromics.com". So the zone confirmes the not-existence of that Wildcard-expansion. Bitmap: CNAME, RRSIG, NSEC Validated: RRSIG-Owner _domainconnect.synpromics.com., Algorithm: 13, 3 Labels, original TTL: 600 sec, Signature-expiration: 08.12.2023, 15:56:30 +, Signature-Inception: 23.11.2023, 15:56:30 +, KeyTag 14694, Signer-Name: synpromics.com


	Status: Good. NXDomain-Proof required and found.


	CAA-Query sends a valid NSEC RR as result with the query name "synpromics.com" equal the NSEC-owner "synpromics.com" and the NextOwner "_acme-challenge.synpromics.com". 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: NS, SOA, RRSIG, NSEC, DNSKEY, CDS, CDNSKEY Validated: RRSIG-Owner synpromics.com., Algorithm: 13, 2 Labels, original TTL: 600 sec, Signature-expiration: 08.12.2023, 15:56:30 +, Signature-Inception: 23.11.2023, 15:56:30 +, KeyTag 14694, Signer-Name: synpromics.com


	Status: Good. NoData-Proof required and found.

Zone: www.synpromics.com
www.synpromics.com	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 "synpromics.com" and the NextOwner "_acme-challenge.synpromics.com". So the parent zone confirmes the non-existence of a DS RR. Bitmap: NS, SOA, RRSIG, NSEC, DNSKEY, CDS, CDNSKEY


	RRSIG Type 5 validates the CNAME - Result: synpromics.com Validated: RRSIG-Owner www.synpromics.com., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 08.12.2023, 15:56:30 +, Signature-Inception: 23.11.2023, 15:56:30 +, KeyTag 14694, Signer-Name: synpromics.com

3. Name Servers

Domain	Nameserver	NS-IP
synpromics.com	• ns33.domaincontrol.com / hex:0D 70 31 31	97.74.106.17 Tempe/Arizona/United States (US) - Host Europe GmbH	•
	•	2603:5:21a1::11 Tempe/Arizona/United States (US) - Host Europe GmbH	•
	• ns34.domaincontrol.com / hex:0D 70 32 30	173.201.74.17 Tempe/Arizona/United States (US) - Host Europe GmbH	•
	•	2603:5:22a1::11 Tempe/Arizona/United States (US) - Host Europe GmbH	•
com	• a.gtld-servers.net / nnn1-par6		•
	• b.gtld-servers.net / nnn1-eltxl1		•
	• c.gtld-servers.net / nnn1-par6		•
	• d.gtld-servers.net / nnn1-par6		•
	• e.gtld-servers.net / nnn1-par6		•
	• f.gtld-servers.net / nnn1-defra-4		•
	• g.gtld-servers.net / nnn1-defra-4		•
	• h.gtld-servers.net / nnn1-defra-4		•
	• i.gtld-servers.net / nnn1-defra-4		•
	• j.gtld-servers.net / nnn1-gblon-3		•
	• k.gtld-servers.net / nnn1-gblon-3		•
	• l.gtld-servers.net / nnn1-gblon-3		•
	• m.gtld-servers.net / nnn1-gblon-3		•

4. SOA-Entries

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

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

Domain:	synpromics.com
Zone-Name:	synpromics.com
Primary:	ns33.domaincontrol.com
Mail:	dns.jomax.net
Serial:	2023112217
Refresh:	28800
Retry:	7200
Expire:	604800
TTL:	600
num Entries:	4

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 "synpromics.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: 89449 (complete: 231048)
A	Good: All ip addresses are public addresses
A	Good: 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.
B	No _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.synpromics.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
A	Info:: 29 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
A	Info:: 29 Queries complete, 29 with IPv6, 0 with IPv4.
A	Good: All DNS Queries done via IPv6.
	Bad (greater 8):: An average of 14.5 queries per domain name server required to find all ip addresses of all name servers.
A	Info:: 2 different Name Servers found: ns33.domaincontrol.com, ns34.domaincontrol.com, 2 Name Servers included in Delegation: ns33.domaincontrol.com, ns34.domaincontrol.com, 2 Name Servers included in 1 Zone definitions: ns33.domaincontrol.com, ns34.domaincontrol.com, 1 Name Servers listed in SOA.Primary: ns33.domaincontrol.com.
A	Good: Only one SOA.Primary Name Server found.: ns33.domaincontrol.com.
A	Good: SOA.Primary Name Server included in the delegation set.: ns33.domaincontrol.com.
A	Good: 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: ns33.domaincontrol.com, ns34.domaincontrol.com
A	Good: All Name Server Domain Names have a Public Suffix.
A	Good: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
A	Good: All Name Server ip addresses are public.
A	Good: Minimal 2 different name servers (public suffix and public ip address) found: 2 different Name Servers found
A	Good: 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: 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: domaincontrol.com
	Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: US
A	Info: Ipv4-Subnet-list: 2 Name Servers, 2 different subnets (first Byte): 173., 97., 2 different subnets (first two Bytes): 173.201., 97.74., 2 different subnets (first three Bytes): 173.201.74., 97.74.106.
A	Excellent: Every Name Server IPv4-address starts with an unique Byte.
A	Info: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2603:, 1 different subnets (first two blocks): 2603:0005:, 2 different subnets (first three blocks): 2603:0005:21a1:, 2603:0005:22a1:, 2 different subnets (first four blocks): 2603:0005:21a1:0000:, 2603:0005:22a1:0000:
A	Good: Name Server IPv6 addresses from different subnets found.
A	Good: Nameserver supports TCP connections: 4 good Nameserver
A	Good: Nameserver supports Echo Capitalization: 4 good Nameserver
A	Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver
A	Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 4 good Nameserver
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.
	4. Content- and Performance-critical Checks
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: 59540 milliseconds, 59.540 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. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ns33.domaincontrol.com, ns34.domaincontrol.com

QNr.	Domain	Type	NS used
1	com	NS	l.root-servers.net (2001:500:9f::42)
	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	ns33.domaincontrol.com	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: a1-245.akam.net, a11-64.akam.net, a20-65.akam.net, a6-66.akam.net, a8-67.akam.net, a9-67.akam.net, ans01.domaincontrol.com, ans02.domaincontrol.com
	Answer: ans01.domaincontrol.com 2603:5:2111::23, 97.74.97.35
	Answer: ans02.domaincontrol.com 173.201.65.35, 2603:5:2211::23
3	ns34.domaincontrol.com	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: a1-245.akam.net, a11-64.akam.net, a20-65.akam.net, a6-66.akam.net, a8-67.akam.net, a9-67.akam.net, ans01.domaincontrol.com, ans02.domaincontrol.com
	Answer: ans01.domaincontrol.com 2603:5:2111::23, 97.74.97.35
	Answer: ans02.domaincontrol.com 173.201.65.35, 2603:5:2211::23
4	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
5	a1-245.akam.net	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a4-67.akam.net, a6-67.akam.net
	Answer: a1-67.akam.net 193.108.91.67, 2600:1401:2::43
	Answer: a11-67.akam.net 2600:1480:1::43, 84.53.139.67
	Answer: a12-67.akam.net 184.26.160.67, 2600:1480:f000::43
	Answer: a18-67.akam.net 2600:1480:4800::43, 95.101.36.67
	Answer: a22-67.akam.net 23.211.61.67, 2600:1480:7800::43
	Answer: a28-67.akam.net 2600:1480:d800::43, 95.100.173.67
	Answer: a4-67.akam.net 2600:1480:9000::43, 72.246.46.67
6	a11-64.akam.net	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a4-67.akam.net, a6-67.akam.net
	Answer: a1-67.akam.net 193.108.91.67, 2600:1401:2::43
	Answer: a11-67.akam.net 2600:1480:1::43, 84.53.139.67
	Answer: a12-67.akam.net 184.26.160.67, 2600:1480:f000::43
	Answer: a18-67.akam.net 2600:1480:4800::43, 95.101.36.67
	Answer: a22-67.akam.net 23.211.61.67, 2600:1480:7800::43
	Answer: a28-67.akam.net 2600:1480:d800::43, 95.100.173.67
	Answer: a4-67.akam.net 2600:1480:9000::43, 72.246.46.67
7	a20-65.akam.net	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a4-67.akam.net, a6-67.akam.net
	Answer: a1-67.akam.net 193.108.91.67, 2600:1401:2::43
	Answer: a11-67.akam.net 2600:1480:1::43, 84.53.139.67
	Answer: a12-67.akam.net 184.26.160.67, 2600:1480:f000::43
	Answer: a18-67.akam.net 2600:1480:4800::43, 95.101.36.67
	Answer: a22-67.akam.net 23.211.61.67, 2600:1480:7800::43
	Answer: a28-67.akam.net 2600:1480:d800::43, 95.100.173.67
	Answer: a4-67.akam.net 2600:1480:9000::43, 72.246.46.67
8	a6-66.akam.net	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a4-67.akam.net, a6-67.akam.net
	Answer: a1-67.akam.net 193.108.91.67, 2600:1401:2::43
	Answer: a11-67.akam.net 2600:1480:1::43, 84.53.139.67
	Answer: a12-67.akam.net 184.26.160.67, 2600:1480:f000::43
	Answer: a18-67.akam.net 2600:1480:4800::43, 95.101.36.67
	Answer: a22-67.akam.net 23.211.61.67, 2600:1480:7800::43
	Answer: a28-67.akam.net 2600:1480:d800::43, 95.100.173.67
	Answer: a4-67.akam.net 2600:1480:9000::43, 72.246.46.67
9	a8-67.akam.net	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a4-67.akam.net, a6-67.akam.net
	Answer: a1-67.akam.net 193.108.91.67, 2600:1401:2::43
	Answer: a11-67.akam.net 2600:1480:1::43, 84.53.139.67
	Answer: a12-67.akam.net 184.26.160.67, 2600:1480:f000::43
	Answer: a18-67.akam.net 2600:1480:4800::43, 95.101.36.67
	Answer: a22-67.akam.net 23.211.61.67, 2600:1480:7800::43
	Answer: a28-67.akam.net 2600:1480:d800::43, 95.100.173.67
	Answer: a4-67.akam.net 2600:1480:9000::43, 72.246.46.67
10	a9-67.akam.net	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a4-67.akam.net, a6-67.akam.net
	Answer: a1-67.akam.net 193.108.91.67, 2600:1401:2::43
	Answer: a11-67.akam.net 2600:1480:1::43, 84.53.139.67
	Answer: a12-67.akam.net 184.26.160.67, 2600:1480:f000::43
	Answer: a18-67.akam.net 2600:1480:4800::43, 95.101.36.67
	Answer: a22-67.akam.net 23.211.61.67, 2600:1480:7800::43
	Answer: a28-67.akam.net 2600:1480:d800::43, 95.100.173.67
	Answer: a4-67.akam.net 2600:1480:9000::43, 72.246.46.67
11	a6-67.akam.net	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a4-67.akam.net, a6-67.akam.net
	Answer: a1-67.akam.net 193.108.91.67, 2600:1401:2::43
	Answer: a11-67.akam.net 2600:1480:1::43, 84.53.139.67
	Answer: a12-67.akam.net 184.26.160.67, 2600:1480:f000::43
	Answer: a18-67.akam.net 2600:1480:4800::43, 95.101.36.67
	Answer: a22-67.akam.net 23.211.61.67, 2600:1480:7800::43
	Answer: a28-67.akam.net 2600:1480:d800::43, 95.100.173.67
	Answer: a4-67.akam.net 2600:1480:9000::43, 72.246.46.67
12	a1-245.akam.net: 193.108.91.245	A	a1-67.akam.net (2600:1401:2::43)
13	a1-245.akam.net: 2600:1401:2::f5	AAAA	a1-67.akam.net (2600:1401:2::43)
14	a11-64.akam.net: 84.53.139.64	A	a1-67.akam.net (2600:1401:2::43)
15	a11-64.akam.net: 2600:1480:1::40	AAAA	a1-67.akam.net (2600:1401:2::43)
16	a20-65.akam.net: 95.100.175.65	A	a1-67.akam.net (2600:1401:2::43)
17	a20-65.akam.net: 2a02:26f0:67::41	AAAA	a1-67.akam.net (2600:1401:2::43)
18	a6-66.akam.net: 23.211.133.66	A	a1-67.akam.net (2600:1401:2::43)
19	a6-66.akam.net: 2600:1401:1::42	AAAA	a1-67.akam.net (2600:1401:2::43)
20	a8-67.akam.net: 2.16.40.67	A	a1-67.akam.net (2600:1401:2::43)
21	a8-67.akam.net: 2600:1403:a::43	AAAA	a1-67.akam.net (2600:1401:2::43)
22	a9-67.akam.net: 184.85.248.67	A	a1-67.akam.net (2600:1401:2::43)
23	a9-67.akam.net: 2a02:26f0:117::43	AAAA	a1-67.akam.net (2600:1401:2::43)
24	a6-67.akam.net: 23.211.133.67	A	a1-67.akam.net (2600:1401:2::43)
25	a6-67.akam.net: 2600:1401:1::43	AAAA	a1-67.akam.net (2600:1401:2::43)
26	ns33.domaincontrol.com: 97.74.106.17	A	a1-245.akam.net (2600:1401:2::f5)
27	ns33.domaincontrol.com: 2603:5:21a1::11	AAAA	a1-245.akam.net (2600:1401:2::f5)
28	ns34.domaincontrol.com: 173.201.74.17	A	a1-245.akam.net (2600:1401:2::f5)
29	ns34.domaincontrol.com: 2603:5:22a1::11	AAAA	a1-245.akam.net (2600:1401:2::f5)

13. CAA - Entries

Domainname	flag	Value	∑ Queries
www.synpromics.com			1
synpromics.com	0	no CAA entry found	1
com	0	no CAA entry found	1

14. TXT - Entries

Domainname	TXT Entry	Status	∑ Queries
synpromics.com		ok	1
www.synpromics.com			1
_acme-challenge.synpromics.com	(le_godaddy_dns) please delete me	missing entry or wrong length	1
_acme-challenge.www.synpromics.com		Name Error - The domain name does not exist	1
_acme-challenge.synpromics.com.synpromics.com		Name Error - The domain name does not exist	1
_acme-challenge.www.synpromics.com.synpromics.com		Name Error - The domain name does not exist	1
_acme-challenge.www.synpromics.com.www.synpromics.com		Name Error - The domain name does not exist	1

15. DomainService - Entries

No DomainServiceEntries entries found

16. Cipher Suites

No Ciphers found

17. Portchecks

No open Ports <> 80 / 443 found, so no additional Ports checked.

Permalink: https://check-your-website.server-daten.de/?i=ae410194-9bd2-47cb-88f0-6a7a6e29c44b

Last Result: https://check-your-website.server-daten.de/?q=synpromics.com - 2023-11-23 16:56:53

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

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