equifax.co.in security report

Certificate, security headers, email authentication, DNS, registration, and exposed hosts — from public sources.

18risk

Low

Minor observations only.

0Critical

0High

1Medium

20Low

1Info

Collected 8 hours ago3.1sfrom cache

Headers—

unavailable

Certificate Transparency64
DNS resolution16
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs12
Registration
DNS posture10
Email authentication2
Certificate
Security headers
Archived URLs
Analysis22

noteFound 64 hostnames; this runtime allows 50 outbound requests per scan, so the 21 most likely to matter were resolved.
noteCertificate inspection is unavailable in this runtime.
noteNetwork ownership lookup is unavailable in this runtime; ASN and org are omitted.
noteCDN/WAF detection is unavailable in this runtime.
noteSecurity headers did not complete (Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits). Results below are partial.

Receivers are asked to report spoofing but not to block it. This is the right first step, and the wrong place to stop.
What to do
Once reports look clean, move to p=quarantine, then p=reject.
asset: equifax.co.in
api.qa.equifax.co.in appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: api.qa.equifax.co.in
api.dev.equifax.co.in appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: api.dev.equifax.co.in
api.uat.equifax.co.in appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: api.uat.equifax.co.in
kfe-uat.equifax.co.in appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: kfe-uat.equifax.co.in
uat.icsaas.equifax.co.in appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: uat.icsaas.equifax.co.in
api.sandbox.equifax.co.in appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: api.sandbox.equifax.co.in
uat-icindia.equifax.co.in appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: uat-icindia.equifax.co.in
business-uat.equifax.co.in appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: business-uat.equifax.co.in
uat-clientgw.equifax.co.in appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: uat-clientgw.equifax.co.in
dev.developer.equifax.co.in appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: dev.developer.equifax.co.in
uat.developer.equifax.co.in appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: uat.developer.equifax.co.in
test.developer.equifax.co.in appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: test.developer.equifax.co.in
anav.uat.icsaas.equifax.co.in appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: anav.uat.icsaas.equifax.co.in
api-hrsol.uat.in.equifax.co.in appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: api-hrsol.uat.in.equifax.co.in
business-api-uat.equifax.co.in appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: business-api-uat.equifax.co.in
qa.microservices.equifax.co.in appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: qa.microservices.equifax.co.in
cpui-business-uat.equifax.co.in appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: cpui-business-uat.equifax.co.in
dev.microservices.equifax.co.in appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: dev.microservices.equifax.co.in
smarts.uat.icsaas.equifax.co.in appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: smarts.uat.icsaas.equifax.co.in
Answers for this domain are not signed, so a resolver cannot tell a forged response from a real one.
What to do
Enable DNSSEC at your DNS host and publish the DS record at the registrar.
asset: equifax.co.in
Any public certificate authority may issue certificates for this domain. CAA lets you name the ones allowed to.
What to do
Add a CAA record naming your CA, e.g. `0 issue "letsencrypt.org"`.
asset: equifax.co.in

–No MX records — domain does not receive mail
!SPFends in ~all
v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com ~all
!DMARCp=none
v=DMARC1; p=none; rua=mailto:dmarc_rua@emaildefense.proofpoint.com; ruf=mailto:dmarc_ruf@emaildefense.proofpoint.com;fo=1
–MTA-STSn/a

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓10 nameservers
a1-111.akam.net a11-64.akam.net a14-64.akam.net a16-66.akam.net a3-66.akam.net a4-66.akam.net+4

✓Registered with MarkMonitor Inc.19.6 years old
equifax.co.in
✓Registration expiry522 days
2028-02-11
✓Transfer lock
client update prohibited, client delete prohibited, client transfer prohibited
✓4 nameservers at registry
pdns105.ultradns.biz pdns105.ultradns.com pdns105.ultradns.net pdns105.ultradns.org

Address	Ports	Edge	Network
147.146.240.141 equifax.co.in +1	80443	direct	—
35.244.54.222 api.uat.equifax.co.in +7	80443	direct	—
147.146.251.197 uat-icindia.equifax.co.in	80443	direct	—
147.146.251.193 business-uat.equifax.co.in	80443	direct	—
147.146.251.199 uat-clientgw.equifax.co.in	80443	direct	—
147.146.251.194 business-api-uat.equifax.co.in	80443	direct	—
14.143.213.173 kfe-uat.equifax.co.in	none known	direct	—
121.241.250.188 uat.icsaas.equifax.co.in	none known	direct	—
121.242.118.197 anav.uat.icsaas.equifax.co.in	none known	direct	—
14.143.213.170 qa.microservices.equifax.co.in	none known	direct	—
14.143.213.169 dev.microservices.equifax.co.in	none known	direct	—
121.241.250.190 smarts.uat.icsaas.equifax.co.in	none known	direct	—

Archived URLs

Endpoints the Wayback Machine has kept — config files, backups, scripts. Slow to fetch, so it is here on request.

equifax.co.in security report

Low

Findings

Email authentication

DNS

Registration

Hosts

Hostnames