SSL Check WHOIS
Dashboard / Security Report

www.dayforce.com

Add this badge to your site

Shows this report's grade and links back to it. It is read from the stored report, never a new scan; a report older than 30 days also shows the month it was checked.

www.dayforce.com: SSL/TLS grade A+ (HTTPS Monitor)www.dayforce.comA+
IPv6: no public AAAA record — the domain is reachable over IPv4 only.
All 8 endpoints share identical configuration Select an IP for owner, ASN & location
A+ 170.153.144.0 IPv4 WHOIS › A+ 170.153.144.1 IPv4 WHOIS › A+ 170.153.144.10 IPv4 WHOIS › A+ 170.153.144.11 IPv4 WHOIS › A+ 170.153.144.12 IPv4 WHOIS › A+ 170.153.144.13 IPv4 WHOIS › A+ 170.153.144.14 IPv4 WHOIS › A+ 170.153.144.15 IPv4 WHOIS ›

Grade Breakdown

Protocol Support 95%
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_256_GCM_SHA384

Protocol Details

Connection
ALPN h2 http/1.1
SNI Required Yes
Supported Named Groups X25519MLKEM768 X25519Kyber768Draft00 x25519 secp256r1 secp384r1 secp521r1 (server preference order)
Post-Quantum Key Exchange Yes X25519MLKEM768, X25519Kyber768Draft00
HTTP/3 (QUIC) No
Encrypted Client Hello No
Security Features
Forward SecrecyYes (ECDHE / DHE)
Downgrade Prevention Yes (legacy TLS disabled)
Secure Renegotiation Supported (RFC 5746)
Extended Master Secret Yes (RFC 7627)
OCSP Stapling Yes
HSTS Yes 1 year · includeSubDomains
HSTS Preloading Not preloadedSubmit →
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
TLS_AES_256_GCM_SHA3840x1302ECDHEFS256Secure
TLS_CHACHA20_POLY1305_SHA2560x1303ECDHEFS256Secure
# TLS 1.2
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA2560xC02BECDHEFS128Secure
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA3840xC02CECDHEFS256Secure

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 7TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Chrome 49 / XP SP3TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
IE 11 / Win 10TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
IE 11 / Win 7TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Android 9.0TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Android 7.0TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Android 5.0TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Android 4.4.2TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Java 11TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
Java 8u121TLS 1.2TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256Success
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)
www.dayforce.com301 → https://www.dayforce.com/ → 200 OK200 OK
dayforce.com301 → https://dayforce.com/ → … → https://www.dayforce.com/ → 200 OK301 → https://www.dayforce.com/ → 200 OK
  • http://www.dayforce.com redirects to HTTPS.

DNS Records

As a public resolver answered for www.dayforce.com and its domain dayforce.com. Looked up 2026-11-21 02:27 UTC · today

TypeRecords
www.dayforce.com
A
AAAA None
MX None
SPF None
dayforce.com
A
AAAA None
NS
ns1-02.azure-dns.com ns2-02.azure-dns.net ns3-02.azure-dns.org ns4-02.azure-dns.info
MX
10 mxa-0001b201.gslb.pphosted.com 10 mxb-0001b201.gslb.pphosted.com
SPF
v=spf1 mx include:docebosaas.com include:_spf.salesforce.com include:spf1.dayforce.com include:aspmx.pardot.com include:cust-spf.exacttarget.com ip4:208.84.65.220 ip4:20.5.80.155 ip4:20.5.82.25 ip4:67.231.152.177 ip4:54.211.103.137 ip4:34.196.213.209 ip4:3.223.159.84 ip4:34.224.161.185 ip4:34.201.178.5 ip4:40.114.119.86 ip4:205.220.183.21 ip4:205.220.171.21 include:aws.us1.spf.staffbase.com ~all

Certificate Identity

Common Namewww.dayforce.com
Alt Names *.dayforce.com dayforce.com
IssuerCN=DigiCert Global G3 TLS ECC SHA384 2020 CA1, O=DigiCert Inc, C=US
Validity 2026-01-06 to 2027-01-05 (45 days remaining)
KeyECDSA 256 bits (sha384ECDSA)
Serial Number0C494B87C86D78CA5A304353AB41BE0E
SHA256 Fingerprint 84bbcfbcc9a2c83b62f667e6350551408bac7970d5b9fa5a24d95801add9af06
Pin SHA256qZOLNj5FgJPyZHSM5sVaTOqffmEWtGsVch51qJ9NTyY=

Certificate Properties

Type OV Organization Validated
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) OCSP: http://ocsp.digicert.com CRL: http://crl3.digicert.com/DigiCertGlobalG3TLSECCSHA3842020CA1-2.crl
DNS CAA Yes (configured) 0 issue "globalsign.com" 0 iodef "mailto:[email protected]" 0 issuewild "digicert.com" 0 issue "digicert.com" 0 issuewild "globalsign.com" 0 issue "pki.goog" 0 issue "letsencrypt.org" 0 issuewild "pki.goog" 0 issuewild "letsencrypt.org" 0 issue "amazon.com" 0 issuewild "amazon.com"
Trusted By Yes Mozilla · Apple · Android · Java · Windows
Name Match Yes
Validity Period 365 days (maximum 398 days for certificates issued then)
Chain IssuesNone

Trust Chain Architecture

End-Entity Certificate
CN=*.dayforce.com, O="Dayforce, Inc.", L=Minneapolis, S=Minnesota, C=US (Issuer: CN=DigiCert Global G3 TLS ECC SHA384 2020 CA1, O=DigiCert Inc, C=US)
Intermediate CA
CN=DigiCert Global G3 TLS ECC SHA384 2020 CA1, O=DigiCert Inc, C=US (Issuer: CN=DigiCert Global Root G3, OU=www.digicert.com, O=DigiCert Inc, C=US)
Root Certificate
CN=DigiCert Global Root G3, OU=www.digicert.com, O=DigiCert Inc, C=US (Issuer: CN=DigiCert Global Root G3, OU=www.digicert.com, O=DigiCert Inc, C=US)

TLS History & Relations

Everything our scans have seen for www.dayforce.com, first seen 2026-11-21; current certificate since 2026-11-21.

Certificates served

Certificate (SHA-256)IssuerValidServed
84bbcfbcc9a2c83b… current DigiCert Global G3 TLS ECC SHA384 2020 CA12026-01-06 → 2027-01-052026-11-21

Addresses

AddressCertificateSeen
170.153.144.0 84bbcfbcc9a2c83b… 2026-11-21
170.153.144.1 84bbcfbcc9a2c83b… 2026-11-21
170.153.144.10 84bbcfbcc9a2c83b… 2026-11-21
170.153.144.11 84bbcfbcc9a2c83b… 2026-11-21
170.153.144.12 84bbcfbcc9a2c83b… 2026-11-21
170.153.144.13 84bbcfbcc9a2c83b… 2026-11-21
170.153.144.14 84bbcfbcc9a2c83b… 2026-11-21
170.153.144.15 84bbcfbcc9a2c83b… 2026-11-21

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

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-21 02:27A+TLS 1.3 84bbcfbcc9a2c83b… 170.153.144.0, 170.153.144.1, 170.153.144.10, 170.153.144.11, 170.153.144.12, 170.153.144.13, 170.153.144.14, 170.153.144.15