SSL Check WHOIS
Dashboard / Security Report

divinemarriagecenter.com

IPv6: no public AAAA record — the domain is reachable over IPv4 only.
All 2 endpoints share identical configuration Select an IP for owner, ASN & location
A+ 15.197.225.128 IPv4 WHOIS › A+ 3.33.251.168 IPv4 WHOIS ›
A+

Exceptional Security

Overall Rating
Assessed 2026-11-17 01:19 UTC

Grade Breakdown

Protocol Support 100%
Key Exchange 90%
Cipher Strength 100%
Certificate 100%

Protocol Configuration

Supported Protocols

TLS 1.3
TLS 1.2
TLS 1.1
TLS 1.0
SSL 3
SSL 2

Negotiated Cipher

TLS_AES_128_GCM_SHA256

Protocol Details

Connection
ALPN No
SNI Required Yes
Supported Named Groups x25519 secp256r1 secp384r1 (inferred)
Post-Quantum Key Exchange Unknown
HTTP/3 (QUIC) No
Encrypted Client Hello No
Security Features
Forward SecrecyYes (ECDHE / DHE)
Downgrade Prevention Yes (legacy TLS disabled)
Secure Renegotiation N/A (TLS 1.3 only — no renegotiation)
Extended Master Secret N/A (built into TLS 1.3)
OCSP Stapling Unknown (measured on TLS 1.2 only)
HSTS Unknown (the HTTPS request to this IP failed)
HSTS Preloading N/A (HSTS not enabled)
Security Checks
BEAST attack Mitigated
POODLE (SSLv3) No (SSL 3 not supported)
POODLE (TLS) No
RC4 No
SSL/TLS CompressionNo (not supported by .NET TLS stack)
HeartbleedNot tested

Cipher Suite Analysis

Cipher SuiteHexKey ExchangeFSBitsStrength
# TLS 1.3
TLS_AES_128_GCM_SHA2560x1301ECDHEFS128Secure

Handshake Simulation

ClientProtocolCipher SuiteResult
Chrome 120 / Win 11TLS 1.3TLS_AES_256_GCM_SHA384Success
Chrome 80 / Win 10TLS 1.3TLS_AES_256_GCM_SHA384Success
Firefox 115 / Win 10TLS 1.3TLS_AES_256_GCM_SHA384Success
iOS 17 / SafariTLS 1.3TLS_CHACHA20_POLY1305_SHA256Success
macOS 14 / SafariTLS 1.3TLS_AES_256_GCM_SHA384Success
Android 14TLS 1.3TLS_AES_128_GCM_SHA256Success
Chrome 69 / Win 7--No
Chrome 49 / XP SP3--No
IE 11 / Win 10--No
IE 11 / Win 7--No
Android 9.0--No
Android 7.0--No
Android 5.0--No
Android 4.4.2--No
Java 11--No
Java 8u121--No
Android 4.0.4--No
Android 4.1.1--No
Baidu Jan 2015--No
Java 6--No

* Simulated based on server's supported protocols and cipher configuration.

Site Access: HTTP and HTTPS

What a visitor typing each address gets, and where its redirects end (up to 5 are followed), as seen from our scanner.

Hosthttp:// (port 80)https:// (port 443)
divinemarriagecenter.com301 → https://www.itsadivinelife.com/ → 200 OK301 → https://www.itsadivinelife.com/ → 200 OK
www.divinemarriagecenter.com301 → https://www.divinemarriagecenter.com/ → … → https://www.itsadivinelife.com/ → 200 OK301 → https://divinemarriagecenter.com/ → … → https://www.itsadivinelife.com/ → 200 OK
  • http://divinemarriagecenter.com redirects to HTTPS.
  • https://divinemarriagecenter.com forwards visitors to www.itsadivinelife.com, a different site. View its report ›

DNS Records

As a public resolver answered for divinemarriagecenter.com. Looked up 2026-11-17 01:19 UTC · today

TypeRecords
A
AAAA None
NS
ns01.domaincontrol.com ns02.domaincontrol.com
MX
1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 10 alt3.aspmx.l.google.com 10 alt4.aspmx.l.google.com
SPF
v=spf1 include:dc-aa8e722993._spfm.divinemarriagecenter.com ~all

Certificate Identity

Common Namedivinemarriagecenter.com
Alt Names divinemarriagecenter.com
IssuerCN=GoDaddy TLS Intermediate CA DV - R1v1, O=GoDaddy.com, C=US
Validity 2026-08-07 to 2027-02-21 (96 days remaining)
KeyRSA 2048 bits (sha256RSA)
Serial Number4B101F49D1827746
SHA256 Fingerprint 0d2e37f9103efa51a81345d543e3e19fdfb61a4fca89bb9a2125e576072c8754
Pin SHA256iRUFsdlkhQ9YLzOOQEh9qDapktvtewIFYohT5T1p/9I=

Certificate Properties

Type DV
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) OCSP: http://ocsp.godaddy.com/ CRL: http://crl.godaddy.com/gdr1v1dv_s1-12.crl
DNS CAA No (missing)
Trusted By Yes Mozilla · Apple · Android · Java · Windows
Name Match Yes
Validity Period 198 days (maximum 200 days for certificates issued then)
Chain Issues
• Contains anchor (root CA included in chain)

Trust Chain Architecture

End-Entity Certificate
CN=divinemarriagecenter.com (Issuer: CN=GoDaddy TLS Intermediate CA DV - R1v1, O=GoDaddy.com, C=US)
Intermediate CA
CN=GoDaddy TLS Intermediate CA DV - R1v1, O=GoDaddy.com, C=US (Issuer: CN=GoDaddy TLS Root CA - R1, O=GoDaddy.com, C=US)
Intermediate CA
CN=GoDaddy TLS Root CA - R1, O=GoDaddy.com, C=US (Issuer: CN=Go Daddy Root Certificate Authority - G2, O="GoDaddy.com, Inc.", L=Scottsdale, S=Arizona, C=US)
Root Certificate
CN=Go Daddy Root Certificate Authority - G2, O="GoDaddy.com, Inc.", L=Scottsdale, S=Arizona, C=US (Issuer: CN=Go Daddy Root Certificate Authority - G2, O="GoDaddy.com, Inc.", L=Scottsdale, S=Arizona, C=US)

TLS History & Relations

Everything our scans have seen for divinemarriagecenter.com, first seen 2026-11-17; current certificate since 2026-11-17.

Certificates served

Certificate (SHA-256)IssuerValidServed
0d2e37f9103efa51… current GoDaddy TLS Intermediate CA DV - R1v12026-08-07 → 2027-02-212026-11-17

Addresses

AddressCertificateSeen
3.33.251.168 0d2e37f9103efa51… 2026-11-17
15.197.225.128 0d2e37f9103efa51… 2026-11-17

TLS history (a row per change; repeated checks only extend it)

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-17 01:19A+TLS 1.3 0d2e37f9103efa51… 3.33.251.168, 15.197.225.128

Other hosts seen on the same addresses