Last Updated: April 19, 2024
yalelawjournal.org has 5 NS records, 1 A records, 0 AAAA records, 5 MX records, and 0 TXT records. Name servers for yalelawjournal.org are ns3.dnsmadeeasy.com, ns4.dnsmadeeasy.com, ns1.dnsmadeeasy.com, ns0.dnsmadeeasy.com, ns2.dnsmadeeasy.com. A records for yalelawjournal.org are 45.56.73.124. MX records that process @yalelawjournal.org email are aspmx2.googlemail.com, aspmx3.googlemail.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, aspmx.l.google.com. We have observed yalelawjournal.org to have 4 subdomains. A subdomain count of 4 is considered a small digital footprint. yalelawjournal.org domain rank of 19,136 makes it valuable phishing target. Typosquat domains for yalelawjournal.org may look like xn--alelawjournl-qcb06r.org, xn--alelawjournl-ntd40y.org, xn--alelawjournl-zob227b.org, xn--alelawjournl-3cb6898h.org, xn--alelawjournl-dcb4788h.org. As of April 19, 2024, yalelawjournal.org does not have any threat intelligence reports of concern.
Search DigitalStakeout Footprint to find another asset.
45.56.73.124
No DNS AAAA records
aspmx2.googlemail.com
aspmx3.googlemail.com
alt1.aspmx.l.google.com
alt2.aspmx.l.google.com
aspmx.l.google.com
ns3.dnsmadeeasy.com
ns4.dnsmadeeasy.com
ns1.dnsmadeeasy.com
ns0.dnsmadeeasy.com
ns2.dnsmadeeasy.com
No DNS TXT records
yalelawjournal.org has 4 subdomains in our inventory.
nginx
United States
{"message_type": "certificate_update", "data": {"leaf_cert": {"not_after": 1690816849, "signature_algorithm": "sha256, rsa", "extensions": {"subjectKeyIdentifier": "4C:C4:BC:C3:C1:6D:4B:73:E6:54:07:76:4B:02:8F:93:BD:29:D2:46", "authorityKeyIdentifier": "keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6\n", "extendedKeyUsage": "TLS Web server authentication, TLS Web client authentication", "subjectAltName": "DNS:yalelawjournal.org, DNS:www.yalelawjournal.org, DNS:admin.yalelawjournal.org", "keyUsage": "Digital Signature, Key Encipherment", "certificatePolicies": "Policy: 1.3.6.1.4.1.44947.1.1.1\n CPS: http://cps.letsencrypt.org", "ctlPoisonByte": true, "authorityInfoAccess": "CA Issuers - URI:http://r3.i.lencr.org/\nOCSP - URI:http://r3.o.lencr.org\n", "basicConstraints": "CA:FALSE"}, "fingerprint": "20:CD:05:DC:9B:68:E8:C8:AF:7C:B2:81:4D:23:BC:06:07:09:B2:48", "all_domains": ["admin.yalelawjournal.org", "www.yalelawjournal.org", "yalelawjournal.org"], "serial_number": "433A7C54BED5E36D9ECC2AF42A8878FC789", "subject": {"C": null, "CN": "yalelawjournal.org", "L": null, "O": null, "ST": null, "emailAddress": null, "OU": null, "aggregated": "/CN=yalelawjournal.org"}, "not_before": 1683040850, "issuer": {"C": "US", "CN": "R3", "L": null, "O": "Let's Encrypt", "ST": null, "emailAddress": null, "OU": null, "aggregated": "/C=US/CN=R3/O=Let's Encrypt"}}, "cert_link": "https://oak.ct.letsencrypt.org/2023/ct/v1/get-entries?start=554109947&end=554109947", "source": {"url": "https://oak.ct.letsencrypt.org/2023/", "name": "Let's Encrypt 'Oak2023' log"}, "update_type": "PrecertLogEntry", "seen": 1683044480.502469, "cert_index": 554109947}}