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


 

 

Y

 

Private IP-Address found

 

Checked:
20.11.2023 05:11:45

 

Older results

No older results found

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
files-pre.pintek.id
A
10.50.0.4
No Hostname found
yes
1
0

AAAA

yes


www.files-pre.pintek.id

Name Error
yes
1
0
*.pintek.id
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


*.files-pre.pintek.id
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: 01.12.2023, 00:00:00 +, Signature-Inception: 10.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: id

id
1 DS RR in the parent zone found






DS with Algorithm 8, KeyTag 26887, DigestType 2 and Digest KL4iADoa+x7Zp7uCSCJ04ttfCabFBwLHMeBA0iVzR+o=






1 RRSIG RR to validate DS RR found






RRSIG-Owner id., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 02.12.2023, 17:00:00 +, Signature-Inception: 19.11.2023, 16: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 22449, Flags 256






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






2 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner id., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 10.12.2023, 12:27:15 +, Signature-Inception: 10.11.2023, 12:25:05 +, KeyTag 22449, Signer-Name: id






RRSIG-Owner id., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 10.12.2023, 12:27:15 +, Signature-Inception: 10.11.2023, 12:25:05 +, KeyTag 26887, Signer-Name: id






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






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






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



Zone: pintek.id

pintek.id
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 "pintek.id" and the NextOwner "pinten.id". So the parent zone confirmes the non-existence of a DS RR.
Bitmap: NS, RRSIG, NSEC






0 DNSKEY RR found









Zone: files-pre.pintek.id

files-pre.pintek.id
0 DS RR in the parent zone found






0 DNSKEY RR found









Zone: www.files-pre.pintek.id

www.files-pre.pintek.id
0 DS RR in the parent zone found

 

3. Name Servers

DomainNameserverNS-IP
www.files-pre.pintek.id
  ns-cloud-c1.googledomains.com

files-pre.pintek.id
  ns-cloud-c1.googledomains.com
216.239.32.108
Mountain View/California/United States (US) - Google LLC


 
2001:4860:4802:32::6c
Montreal/Quebec/Canada (CA) - Google LLC

pintek.id
  ns-cloud-c1.googledomains.com
216.239.32.108
Mountain View/California/United States (US) - Google LLC


 
2001:4860:4802:32::6c
Montreal/Quebec/Canada (CA) - Google LLC


  ns-cloud-c2.googledomains.com
216.239.34.108
Mountain View/California/United States (US) - Google LLC


 
2001:4860:4802:34::6c
Montreal/Quebec/Canada (CA) - Google LLC


  ns-cloud-c3.googledomains.com
216.239.36.108
Mountain View/California/United States (US) - Google LLC


 
2001:4860:4802:36::6c
Montreal/Quebec/Canada (CA) - Google LLC


  ns-cloud-c4.googledomains.com
216.239.38.108
Mountain View/California/United States (US) - Google LLC


 
2001:4860:4802:38::6c
Montreal/Quebec/Canada (CA) - Google LLC

id
  b.dns.id / s-201


  c.dns.id / h-204


T  d.dns.id / b-101


  e.dns.id / j-107


  ns4.apnic.net / ns4-cdg.apnic.net

 

4. SOA-Entries


Domain:id
Zone-Name:id
Primary:b.dns.id
Mail:hostmaster.pandi.id
Serial:2023382736
Refresh:28800
Retry:7200
Expire:604800
TTL:172800
num Entries:5


Domain:pintek.id
Zone-Name:pintek.id
Primary:ns-cloud-c1.googledomains.com
Mail:cloud-dns-hostmaster.google.com
Serial:2
Refresh:21600
Retry:3600
Expire:259200
TTL:300
num Entries:8


Domain:files-pre.pintek.id
Zone-Name:pintek.id
Primary:ns-cloud-c1.googledomains.com
Mail:cloud-dns-hostmaster.google.com
Serial:2
Refresh:21600
Retry:3600
Expire:259200
TTL:300
num Entries:2


Domain:www.files-pre.pintek.id
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

DomainnameHttp-StatusredirectSec.G








 

7. Comments


1. General Results, most used to calculate the result

Aname "files-pre.pintek.id" is subdomain, public suffix is ".id", top-level-domain is ".id", top-level-domain-type is "country-code", Country is Indonesia, tld-manager is "Perkumpulan Pengelola Nama Domain Internet Indonesia (PANDI)", num .id-domains preloaded: 538 (complete: 231048)
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.
Yfiles-pre.pintek.id

10.50.0.4
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: 10.0.0.0 to 10.255.255.255: Class A - one private net with 16.777.216 adresses
BNo _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.files-pre.pintek.id

2. Header-Checks

U

No https result with http status 2** or 4** (standard-check) found, no header checked.

3. DNS- and NameServer - Checks

AInfo:: 13 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers.
AInfo:: 13 Queries complete, 13 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
Ok (4 - 8):: An average of 3.3 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 4 different Name Servers found: ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com, 2 Name Servers included in Delegation: ns-cloud-c1.googledomains.com, ns-cloud-c4.googledomains.com, 4 Name Servers included in 1 Zone definitions: ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com, 1 Name Servers listed in SOA.Primary: ns-cloud-c1.googledomains.com.
AGood: Only one SOA.Primary Name Server found.: ns-cloud-c1.googledomains.com.
AGood: SOA.Primary Name Server included in the delegation set.: ns-cloud-c1.googledomains.com.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns-cloud-c1.googledomains.com (216.239.32.108): Delegation: ns-cloud-c1.googledomains.com, ns-cloud-c4.googledomains.com, Zone: ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com. Name Servers defined in Zone, missing in Delegation: ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns-cloud-c1.googledomains.com (2001:4860:4802:32::6c): Delegation: ns-cloud-c1.googledomains.com, ns-cloud-c4.googledomains.com, Zone: ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com. Name Servers defined in Zone, missing in Delegation: ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns-cloud-c2.googledomains.com (216.239.34.108): Delegation: ns-cloud-c1.googledomains.com, ns-cloud-c4.googledomains.com, Zone: ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com. Name Servers defined in Zone, missing in Delegation: ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns-cloud-c2.googledomains.com (2001:4860:4802:34::6c): Delegation: ns-cloud-c1.googledomains.com, ns-cloud-c4.googledomains.com, Zone: ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com. Name Servers defined in Zone, missing in Delegation: ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns-cloud-c3.googledomains.com (216.239.36.108): Delegation: ns-cloud-c1.googledomains.com, ns-cloud-c4.googledomains.com, Zone: ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com. Name Servers defined in Zone, missing in Delegation: ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns-cloud-c3.googledomains.com (2001:4860:4802:36::6c): Delegation: ns-cloud-c1.googledomains.com, ns-cloud-c4.googledomains.com, Zone: ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com. Name Servers defined in Zone, missing in Delegation: ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns-cloud-c4.googledomains.com (216.239.38.108): Delegation: ns-cloud-c1.googledomains.com, ns-cloud-c4.googledomains.com, Zone: ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com. Name Servers defined in Zone, missing in Delegation: ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns-cloud-c4.googledomains.com (2001:4860:4802:38::6c): Delegation: ns-cloud-c1.googledomains.com, ns-cloud-c4.googledomains.com, Zone: ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com. Name Servers defined in Zone, missing in Delegation: ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.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: 4 different Name Servers found
AGood: All name servers have ipv4- and ipv6-addresses.: 4 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.: 4 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: googledomains.com
AGood: Name servers with different Country locations found: 4 Name Servers, 2 Countries: CA, US
AInfo: Ipv4-Subnet-list: 4 Name Servers, 1 different subnets (first Byte): 216., 1 different subnets (first two Bytes): 216.239., 4 different subnets (first three Bytes): 216.239.32., 216.239.34., 216.239.36., 216.239.38.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: IPv6-Subnet-list: 4 Name Servers with IPv6, 1 different subnets (first block): 2001:, 1 different subnets (first two blocks): 2001:4860:, 1 different subnets (first three blocks): 2001:4860:4802:, 4 different subnets (first four blocks): 2001:4860:4802:0032:, 2001:4860:4802:0034:, 2001:4860:4802:0036:, 2001:4860:4802:0038:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 2 good Nameserver
AGood: Nameserver supports Echo Capitalization: 2 good Nameserver
XNameserver Timeout checking Echo Capitalization: d.dns.id
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 2 good Nameserver
Nameserver doesn't pass all EDNS-Checks: d.dns.id: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (b-101). COOKIE: fatal timeout. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns-cloud-c1.googledomains.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.

4. 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: 86696 milliseconds, 86.696 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

Issuerlast 7 daysactivenum Certs
CN=R3, O=Let's Encrypt, C=US
0 /0 new
0
1

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
10357735153
leaf cert
CN=R3, O=Let's Encrypt, C=US
2023-08-20 23:45:20
2023-11-19 00:45:19
files-pre.pintek.id
1 entries


 

11. Html-Content - Entries

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

 

12. Html-Parsing via https://validator.w3.org/nu/

Small Code update, wait one minute

 

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.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
ns-cloud-c1.googledomains.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns5.googledomains.com, ns6.googledomains.com, ns7.googledomains.com, ns8.googledomains.com

Answer: ns8.googledomains.com
2001:4860:4802:38::a, 216.239.38.10

Answer: ns7.googledomains.com
2001:4860:4802:36::a, 216.239.36.10

Answer: ns6.googledomains.com
2001:4860:4802:34::a, 216.239.34.10

Answer: ns5.googledomains.com
2001:4860:4802:32::a, 216.239.32.10
3
ns-cloud-c2.googledomains.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns5.googledomains.com, ns6.googledomains.com, ns7.googledomains.com, ns8.googledomains.com

Answer: ns8.googledomains.com
2001:4860:4802:38::a, 216.239.38.10

Answer: ns7.googledomains.com
2001:4860:4802:36::a, 216.239.36.10

Answer: ns6.googledomains.com
2001:4860:4802:34::a, 216.239.34.10

Answer: ns5.googledomains.com
2001:4860:4802:32::a, 216.239.32.10
4
ns-cloud-c3.googledomains.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns5.googledomains.com, ns6.googledomains.com, ns7.googledomains.com, ns8.googledomains.com

Answer: ns8.googledomains.com
2001:4860:4802:38::a, 216.239.38.10

Answer: ns7.googledomains.com
2001:4860:4802:36::a, 216.239.36.10

Answer: ns6.googledomains.com
2001:4860:4802:34::a, 216.239.34.10

Answer: ns5.googledomains.com
2001:4860:4802:32::a, 216.239.32.10
5
ns-cloud-c4.googledomains.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns5.googledomains.com, ns6.googledomains.com, ns7.googledomains.com, ns8.googledomains.com

Answer: ns8.googledomains.com
2001:4860:4802:38::a, 216.239.38.10

Answer: ns7.googledomains.com
2001:4860:4802:36::a, 216.239.36.10

Answer: ns6.googledomains.com
2001:4860:4802:34::a, 216.239.34.10

Answer: ns5.googledomains.com
2001:4860:4802:32::a, 216.239.32.10
6
ns-cloud-c1.googledomains.com: 216.239.32.108
A
ns5.googledomains.com (2001:4860:4802:32::a)
7
ns-cloud-c1.googledomains.com: 2001:4860:4802:32::6c
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)
8
ns-cloud-c2.googledomains.com: 216.239.34.108
A
ns5.googledomains.com (2001:4860:4802:32::a)
9
ns-cloud-c2.googledomains.com: 2001:4860:4802:34::6c
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)
10
ns-cloud-c3.googledomains.com: 216.239.36.108
A
ns5.googledomains.com (2001:4860:4802:32::a)
11
ns-cloud-c3.googledomains.com: 2001:4860:4802:36::6c
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)
12
ns-cloud-c4.googledomains.com: 216.239.38.108
A
ns5.googledomains.com (2001:4860:4802:32::a)
13
ns-cloud-c4.googledomains.com: 2001:4860:4802:38::6c
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
files-pre.pintek.id
0

no CAA entry found
1
0
pintek.id
0

no CAA entry found
1
0
id
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
pintek.id
v=spf1 a include:spf.mailtarget.co include:spf.mandrillapp.com ?all google-site-verification=yi8DL8EgNp-o5bd1FBJRkcvCVcHBqyBzZanJ1bn_obI facebook-domain-verification=d1f5n8lmjumi7694h7nn8hvqyd3cgs
ok
1
0
files-pre.pintek.id

ok
1
0
_acme-challenge.files-pre.pintek.id

Name Error - The domain name does not exist
1
0
_acme-challenge.files-pre.pintek.id.pintek.id

Name Error - The domain name does not exist
1
0
_acme-challenge.files-pre.pintek.id.files-pre.pintek.id

Name Error - The domain name does not exist
1
0

 

16. DomainService - Entries

No DomainServiceEntries entries found

 

 

17. Cipher Suites

No Ciphers found

 

18. Portchecks

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

 

 

Permalink: https://check-your-website.server-daten.de/?i=11ede8a6-2f00-499a-90a9-5ab3d8a47df6

 

Last Result: https://check-your-website.server-daten.de/?q=files-pre.pintek.id - 2023-11-20 05:11:45

 

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

 

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

 

 

Do you really want to support this project? Donate: Check-your-website, IBAN DE98 1001 0010 0575 2211 07, SWIFT/BIC PBNKDEFF, Euro

 

QR-Code of this page - https://check-your-website.server-daten.de/?d=files-pre.pintek.id