Automated public DNS and web checks; results may be incomplete. These are passive observations, not an assessment of the organization.

D63/100

Executive summary

columbia.edu

High exposure. Significant weaknesses put the brand, customers and email at risk.

Full coverage: every applicable check was assessed.

2026-11-15 18:29 UTC

Print report / PDF

Useful for your IT provider or a colleague. Anyone with the link can view the report.

Track your progress

Fix the findings, then come back and rescan. Your scan history is saved in this browser so you can see exactly what improved.

Email security19/30

Needs attention

Spoofing email in the company's name is possible in some cases.

Encryption & certificate18/25

Needs attention

Encryption is in place, but a gap could expose users.

Browser protections23/30

Needs attention

Some browser protections are missing.

DNS infrastructure3/15

Critical

The domain's infrastructure lacks basic protections.

Help someone else check their domain

Share this public report with a colleague. They can review the evidence and check their own domain.

Get the report badge

What to do first

1.
Tell receiving mail servers how to treat fake email from your domain
Without this policy, inboxes have less guidance for spotting messages that impersonate you.
Who can fix it: Your email provider, together with whoever manages your DNS
How to verify after the fix
```
dig +short TXT _dmarc.columbia.edu
```
2.
Send visitors to the secure version of your site
Visitors who type your address without https may stay on an unprotected connection.
Who can fix it: Your web host
How to verify after the fix
```
curl -sI http://columbia.edu/ | grep -iE "^(HTTP|location)"
```

A starting point, not a security guarantee.

What this grade means

Tested hostname: columbia.edu
Website request: GET https://columbia.edu/
Scan time: 2026-11-15 18:29:57 UTC
Grading method: Version 2How grading works
Unverified or excluded checks: None. Every applicable check was assessed.

This is a snapshot of the public configuration checks listed in this report. It does not verify the site's owner, business legitimacy, application security, or absence of vulnerabilities. It is not a security certification.

Get the badge

Show the live grade for columbia.edu in a README, docs or site footer. The badge links to the public report and refreshes every 24 hours.

Scan shown on this page: ⁦2026-11-15 18:29:57 UTC⁩. The badge may display a cached result for up to 24 hours. Open the linked report to check its scan time.

Markdown

[![Domain Armor grade](https://getmirror.online/badge/columbia.edu.svg)](https://getmirror.online/report/columbia.edu)

HTML

<a href="https://getmirror.online/report/columbia.edu"><img src="https://getmirror.online/badge/columbia.edu.svg" alt="Domain Armor grade"></a>

Badge URL

https://getmirror.online/badge/columbia.edu.svg

Scan history

AI fix plan

Pick scans from this browser's history. The AI compares them, explains what changed and builds a prioritized, step-by-step plan.

Scans to analyze

0 of 6 selected

D63/10011/15/26, 06:29 PMCurrent

The current scan is always included.

AI-generated from your scan results only. Review each step before applying it; nothing is sent to or changed on the domain.

Technical detail

Click a check to see the public data, a verification command, a safe fix recommendation and documentation sources.

Email security

19/30

Encryption & certificate

18/25

Browser protections

23/30

DNS infrastructure

3/15

Public DNS records

A	columbia.edu	162.159.128.65 162.159.138.64
AAAA	columbia.edu	—
MX	columbia.edu	10 mxb-00364e01.gslb.pphosted.com 10 mxa-00364e01.gslb.pphosted.com
NS	columbia.edu	auth2.dns.cogentco.com ext-ns1.columbia.edu ns1.lse.ac.uk auth1.dns.cogentco.com
TXT	columbia.edu	adobe-idp-site-verification=c4c82a5f2bf3cc3ee4ad2ee246c28e17ead150faf152556bc9ca5c068762b827 google-site-verification=B93x40FIZF4LI-5cayepjvuwU8ZodIQ09zIDG1gHtIc apple-domain-verification=6W1ObUreaMieGziS fastly-domain-delegation-UzZdOKwpsuzDObCLhWK0-12292020 fastly-domain-delegation-columbia-323594-2020-12-07 ZOOM_verify_H76gKGnfTfSjo0uBs3ATpw ZOOM_verify_aIBp_UI9RA-_nAc54T9CiA ZOOM_verify_ohdpGstzTlO2gNsWqnSiHQ ZOOM_verify_ZJlClnqsRTqo4L8EQGaPDg ZOOM_verify__tMWR0IkQ5mSUFNi7PT0-A wpe-verification=cssrsprod ca3-154a83c0e9b44fa094af06b7a8c9f489 rm_verify=cf192bfd71 intersight=f68fd98601fae5dcfd60cd38f9df964367f5e3ebe94f0cc148eec13f7e11d7e6 ca3-018df5b7d38b415fbe9c920d89e3e815 atlassian-domain-verification=TGY4izz2FIXsrTR48IJgpJMfixggF0xpHJ4TC91Ii5DqZYvIR3zflZ1zbdDNI3NN MS=ms94259742 openai-domain-verification=dv-coLwtcZeuA8rWCUFNhz21TTz google-site-verification=6m_FjnmBT3E6N2cHMf6NxPjSVoWbq4IcRYNlAKT1Dzw wpe-verification=ncdpcolumbia atlassian-domain-verification=3a/aVmiVzaMOzlhAodx3n7lmq1cDotGOHNI3ehzFLzgN7YLZEBEjnxaaqyMmLY9s v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com ~all anthropic-domain-verification-01mqc0=QYIx6Pw50pyhbeOfqjhRRNpve asv=c2f28d3e6fab94ed285140f6a7a2f595 00D36000000XoHU=1TBUw00000001fF 00DVG000008EUsr=1TBVG0000000K0L autodesk-domain-verification=P6lfZ9W5VspsY7qG7oL0 FD558E9C831CB5AFEEF2C5334AEC4B3F 00D3i000000stv6=1TBVK00000003An 00Dj0000001s08g=1TBRN00000006a5 hpe-greenlake-domain-verification=556851666b6c374965566f71625442624d4f683244765178674b706d41507758 asv=beb9ba6971ecdd1dd74f01aec2023d91 google-site-verification=VAzSZlDrZGEFyyON0nW7RwMhOO4d5ysanDVLuqaqoQw ntl-verify-4215bc7bc219630560b478cb158bc927dc970758 MS=ms88535648 google-site-verification=79W02b1NsvPOhVkXxG5gXzAXuxuYquPTXmx_l6KfRok MS=ms32107722 docusign=abbafadf-a495-4889-935f-5fdac37be903 docusign=f8b82e15-b287-46b9-9729-a7436d71c422
TXT	_dmarc.columbia.edu	v=DMARC1; p=none; fo=1; rua=mailto:dmarc_rua@emaildefense.proofpoint.com; ruf=mailto:dmarc_ruf@emaildefense.proofpoint.com;
CAA	columbia.edu	—
DS	columbia.edu	—

Fix priorities

Sorted by risk: severity first, confirmed issues before hardening gaps, then effort and score impact.

1HighHTTP → HTTPS redirectHardening gap+7
2MediumHSTS — enforce encryption in the browserHardening gap+4
3MediumDMARC — anti-spoofing policyHardening gap+10
4MediumDNSSEC — signed DNS recordsHardening gap+7
5LowCAA — who may issue certificatesHardening gap+5
6LowCSP — protection from script injectionHardening gap+3

Indicative alignment

Best-practice mapping of public findings to common frameworks. Passive scanning tests public configuration only; it doesn't prove compliance or a violation.

Google & Yahoo sender rules1 observed gaps
SPF, DKIM and DMARC are required for bulk senders to Gmail and Yahoo; missing them risks rejected or spam-foldered mail.
DMARC — anti-spoofing policy
PCI DSS v4.03 observed gaps
TLS, certificate and browser-header protections relate to PCI DSS v4.0 requirements 4.2 and 6.4 for payment pages.
HTTP → HTTPS redirect HSTS — enforce encryption in the browser CSP — protection from script injection
NIS2 / vendor due diligence4 observed gaps
Vendor risk reviews under NIS2/DORA and cyber-insurance questionnaires check these public signals.
DMARC — anti-spoofing policy HSTS — enforce encryption in the browser DNSSEC — signed DNS records CAA — who may issue certificates
SOC 2 / ISO 27001 baseline3 observed gaps
Baseline external hygiene commonly expected in SOC 2 and ISO 27001 audits.
DMARC — anti-spoofing policy HSTS — enforce encryption in the browser CSP — protection from script injection

Indicative alignment only, based on public configuration. It doesn't establish whether a framework applies to you, and it isn't legal advice, an audit or a certification.

Head-to-head vs competitor

How do you stack up against competitors?

The check reads public data only and makes no changes to the domain. Recommendations are intended for the domain owner.

Is your domain as secure? Scan it free, no sign-up

All pre-scanned domains

What to do first

Tell receiving mail servers how to treat fake email from your domain

Without this policy, inboxes have less guidance for spotting messages that impersonate you.

Who can fix it: Your email provider, together with whoever manages your DNS

How to verify after the fix

dig +short TXT _dmarc.columbia.edu

Send visitors to the secure version of your site

Visitors who type your address without https may stay on an unprotected connection.

Who can fix it: Your web host

How to verify after the fix

curl -sI http://columbia.edu/ | grep -iE "^(HTTP|location)"

What this grade means

Tested hostname

columbia.edu

Website request

GET https://columbia.edu/

Scan time

2026-11-15 18:29:57 UTC

Grading method

Version 2How grading works

Unverified or excluded checks

None. Every applicable check was assessed.

Technical detail

Click a check to see the public data, a verification command, a safe fix recommendation and documentation sources.

Email security

19/30

Encryption & certificate

18/25

Browser protections

23/30

DNS infrastructure

3/15

Public DNS records

A	columbia.edu	162.159.128.65 162.159.138.64
AAAA	columbia.edu	—
MX	columbia.edu	10 mxb-00364e01.gslb.pphosted.com 10 mxa-00364e01.gslb.pphosted.com
NS	columbia.edu	auth2.dns.cogentco.com ext-ns1.columbia.edu ns1.lse.ac.uk auth1.dns.cogentco.com
TXT	columbia.edu	adobe-idp-site-verification=c4c82a5f2bf3cc3ee4ad2ee246c28e17ead150faf152556bc9ca5c068762b827 google-site-verification=B93x40FIZF4LI-5cayepjvuwU8ZodIQ09zIDG1gHtIc apple-domain-verification=6W1ObUreaMieGziS fastly-domain-delegation-UzZdOKwpsuzDObCLhWK0-12292020 fastly-domain-delegation-columbia-323594-2020-12-07 ZOOM_verify_H76gKGnfTfSjo0uBs3ATpw ZOOM_verify_aIBp_UI9RA-_nAc54T9CiA ZOOM_verify_ohdpGstzTlO2gNsWqnSiHQ ZOOM_verify_ZJlClnqsRTqo4L8EQGaPDg ZOOM_verify__tMWR0IkQ5mSUFNi7PT0-A wpe-verification=cssrsprod ca3-154a83c0e9b44fa094af06b7a8c9f489 rm_verify=cf192bfd71 intersight=f68fd98601fae5dcfd60cd38f9df964367f5e3ebe94f0cc148eec13f7e11d7e6 ca3-018df5b7d38b415fbe9c920d89e3e815 atlassian-domain-verification=TGY4izz2FIXsrTR48IJgpJMfixggF0xpHJ4TC91Ii5DqZYvIR3zflZ1zbdDNI3NN MS=ms94259742 openai-domain-verification=dv-coLwtcZeuA8rWCUFNhz21TTz google-site-verification=6m_FjnmBT3E6N2cHMf6NxPjSVoWbq4IcRYNlAKT1Dzw wpe-verification=ncdpcolumbia atlassian-domain-verification=3a/aVmiVzaMOzlhAodx3n7lmq1cDotGOHNI3ehzFLzgN7YLZEBEjnxaaqyMmLY9s v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com ~all anthropic-domain-verification-01mqc0=QYIx6Pw50pyhbeOfqjhRRNpve asv=c2f28d3e6fab94ed285140f6a7a2f595 00D36000000XoHU=1TBUw00000001fF 00DVG000008EUsr=1TBVG0000000K0L autodesk-domain-verification=P6lfZ9W5VspsY7qG7oL0 FD558E9C831CB5AFEEF2C5334AEC4B3F 00D3i000000stv6=1TBVK00000003An 00Dj0000001s08g=1TBRN00000006a5 hpe-greenlake-domain-verification=556851666b6c374965566f71625442624d4f683244765178674b706d41507758 asv=beb9ba6971ecdd1dd74f01aec2023d91 google-site-verification=VAzSZlDrZGEFyyON0nW7RwMhOO4d5ysanDVLuqaqoQw ntl-verify-4215bc7bc219630560b478cb158bc927dc970758 MS=ms88535648 google-site-verification=79W02b1NsvPOhVkXxG5gXzAXuxuYquPTXmx_l6KfRok MS=ms32107722 docusign=abbafadf-a495-4889-935f-5fdac37be903 docusign=f8b82e15-b287-46b9-9729-a7436d71c422
TXT	_dmarc.columbia.edu	v=DMARC1; p=none; fo=1; rua=mailto:dmarc_rua@emaildefense.proofpoint.com; ruf=mailto:dmarc_ruf@emaildefense.proofpoint.com;
CAA	columbia.edu	—
DS	columbia.edu	—

Indicative alignment

Best-practice mapping of public findings to common frameworks. Passive scanning tests public configuration only; it doesn't prove compliance or a violation.

Google & Yahoo sender rules1 observed gaps

SPF, DKIM and DMARC are required for bulk senders to Gmail and Yahoo; missing them risks rejected or spam-foldered mail.

DMARC — anti-spoofing policy

PCI DSS v4.03 observed gaps

TLS, certificate and browser-header protections relate to PCI DSS v4.0 requirements 4.2 and 6.4 for payment pages.

HTTP → HTTPS redirect HSTS — enforce encryption in the browser CSP — protection from script injection

NIS2 / vendor due diligence4 observed gaps

Vendor risk reviews under NIS2/DORA and cyber-insurance questionnaires check these public signals.

DMARC — anti-spoofing policy HSTS — enforce encryption in the browser DNSSEC — signed DNS records CAA — who may issue certificates

SOC 2 / ISO 27001 baseline3 observed gaps

Baseline external hygiene commonly expected in SOC 2 and ISO 27001 audits.

DMARC — anti-spoofing policy HSTS — enforce encryption in the browser CSP — protection from script injection

Indicative alignment only, based on public configuration. It doesn't establish whether a framework applies to you, and it isn't legal advice, an audit or a certification.

columbia.edu

Track your progress

Help someone else check their domain

What to do first

What this grade means

Get the badge

Scan history

AI fix plan

Scans to analyze

Technical detail

Email security

Encryption & certificate

Browser protections

DNS infrastructure

Public DNS records

Is your domain as secure? Scan it free, no sign-up

columbia.edu

Track your progress

Help someone else check their domain

What to do first

What this grade means

Get the badge

Scan history

AI fix plan

Scans to analyze

Technical detail

Email security

Encryption & certificate

Browser protections

DNS infrastructure

Public DNS records

Is your domain as secure? Scan it free, no sign-up

Agent access & discovery signals