Check-Host.cc

Domain

msg.team

Aggregated from public BGP, CT logs, our scan layer, honeypots and global probes.

Run a live full scan of msg.team

On-demand: ports, banners, TLS, tech-stack, subdomains and origin/IP-leak detection. Results are shared publicly for everyone to link to.

Deep-scan now
Hosting IPs
58
A/AAAA targets
Subdomains
517
CT + scan + body
Record Types
3
seen in DNS
Observed Certs
in our scans

DNS Records

A
4.231.24.40, 91.217.27.16
AAAA
MX
NS
ns-1376.awsdns-44.org, ns-1730.awsdns-24.co.uk, ns-73.awsdns-09.com, ns-836.awsdns-40.net
TXT
v=spf1 -all, vkmraslff4ns8dmm2f9380c7f8
CNAME
CAA

WHOIS / Registration

Registration data planned

Registrar, creation/expiry dates and domain status via RDAP. Rolling out gradually — bulk WHOIS is rate-limited, so we resolve on a prioritized cadence.

Subdomains

Every subdomain we know about — harvested from CT-log SANs, scan-observed certs and HTML body references — paired with its current A/AAAA target.

Subdomain Resolves to Last seen
development-guidelines.sp.msg.team 2026-06-04 07:00:56.980
apps.staffing.m4a.msg.team 2026-06-23 11:36:54.109
cmt.msgro.msg.team 2026-07-20 15:42:35.176
api.demo.rokr.msgro.msg.team 2026-06-20 11:34:23.835
api.staging.rokr.msgro.msg.team 2026-05-27 01:16:30.398
api.test.rokr.msgro.msg.team 2026-05-26 10:23:02.310
api-knowledgelake.mgi.msg.team 2026-06-03 21:21:47.117
cdn.bcaas-dev.mgi.msg.team 2026-06-15 22:45:10.123
cm.hub.msg.team 2026-07-23 21:19:40.229
corporate-compliance.mgi.msg.team 2026-06-22 11:49:11.854
data.bcaas-dev.mgi.msg.team 2026-06-15 22:45:10.123
document-tool.mgi.msg.team 2026-05-26 09:51:10.377
msg.team 2026-06-25 20:22:31.777
tendermanager.xai.msg.team 2026-06-17 04:46:58.872
vc.hub.msg.team 2026-07-23 21:28:33.784
www.msg.team 2026-07-22 19:41:26.868
ai-services.mgi.msg.team
1970-01-01 00:00:00.000
ai.msg.team
1970-01-01 00:00:00.000
ai.msg.team.xai.msg.team
1970-01-01 00:00:00.000
api.ai.msg.team
1970-01-01 00:00:00.000
api.ai.msg.team.xai.msg.team
1970-01-01 00:00:00.000
api.ocp.test.tc.gby.msg.team
1970-01-01 00:00:00.000
app.genai-dev.mgi.msg.team
1970-01-01 00:00:00.000
apps.staffingdb-dev.m4a.msg.team
1970-01-01 00:00:00.000
argocd.appfactory.spl.mgi.msg.team 2026-06-15 08:14:01.046
argocd.bcaas-dev.mgi.msg.team
1970-01-01 00:00:00.000
autobahn.docchat.xai.msg.team
1970-01-01 00:00:00.000
avv-check.xai.msg.team
1970-01-01 00:00:00.000
awsdev.msg.team
1970-01-01 00:00:00.000
bais-web.eks.orrp.spl.mgi.msg.team 2026-07-26 20:50:50.811
bbb.vs-02.msg.team
1970-01-01 00:00:00.000
bbsr.gbg.msg.team
1970-01-01 00:00:00.000
bcaas.mgi.msg.team
1970-01-01 00:00:00.000
botserver.gbg.msg.team 2026-07-17 06:32:03.998
build.publicsector.msg.team
1970-01-01 00:00:00.000
cd.hub.msg.team
1970-01-01 00:00:00.000
cd.msg.team 2026-07-22 19:41:26.868
chat.vs-02.msg.team
1970-01-01 00:00:00.000
cit-pisa-hub.pisa-dev.msg.team
1970-01-01 00:00:00.000
citrix.vs-02.msg.team
1970-01-01 00:00:00.000
citrixdirector.vs-02.msg.team
1970-01-01 00:00:00.000
cloud.mgi.msg.team
1970-01-01 00:00:00.000
console.ocp.test.tc.gby.msg.team
1970-01-01 00:00:00.000
console.studio.msg.team 2026-06-18 08:36:42.407
ct-dev.hub.msg.team
1970-01-01 00:00:00.000
daisy.zfa.gbp.msg.team
1970-01-01 00:00:00.000
de.hub.msg.team
1970-01-01 00:00:00.000
default.unicorn.stgespl.spl.mgi.msg.team
1970-01-01 00:00:00.000
dev-int.xai.msg.team
1970-01-01 00:00:00.000
dev.msg.team 2026-07-22 19:41:26.868
dev.xai.msg.team
1970-01-01 00:00:00.000
dev2.pisa.msn.msg.team
1970-01-01 00:00:00.000
docker.msg.team 2026-07-22 19:41:26.868
dockergroup.repo.tc.gby.msg.team
1970-01-01 00:00:00.000
dockerhub.repo.tc.gby.msg.team
1970-01-01 00:00:00.000
dockertc2.repo.tc.gby.msg.team
1970-01-01 00:00:00.000
dora-ki.mgi.msg.team 2026-06-15 23:50:33.036
downloads.ocp.test.tc.gby.msg.team
1970-01-01 00:00:00.000
eftitest.gby.msg.team
1970-01-01 00:00:00.000
feature-uni-2960-test-marzhelm-deployment-with-oracle-db.unicorn.stgespl.spl.mgi.msg.team 2026-06-20 10:25:08.413
finnova.mgi.msg.team
1970-01-01 00:00:00.000
fintract-uat.mgi.msg.team
1970-01-01 00:00:00.000
ftu-daisy.publicsector.msg.team
1970-01-01 00:00:00.000
gbi.msg.team
1970-01-01 00:00:00.000
gbp.msg.team
1970-01-01 00:00:00.000
gbr.msg.team
1970-01-01 00:00:00.000
gbv.msg.team
1970-01-01 00:00:00.000
gby.msg.team
1970-01-01 00:00:00.000
gbzi.mgi.msg.team
1970-01-01 00:00:00.000
genai-dev.mgi.msg.team
1970-01-01 00:00:00.000
genai-uat.mgi.msg.team
1970-01-01 00:00:00.000
genucenter.vs-02.msg.team
1970-01-01 00:00:00.000
genugate.vs-02.msg.team
1970-01-01 00:00:00.000
gg.vs-02.msg.team
1970-01-01 00:00:00.000
git-lhm.publicsector.msg.team
1970-01-01 00:00:00.000
git.gbg.msg.team
1970-01-01 00:00:00.000
github-dev.msg.team 2026-07-24 18:11:24.835
gitlab.msg.team 2026-07-22 19:41:26.868
gitlab.zt.msg.team 2026-06-17 07:29:59.771
gitops.apps.ocp.test.tc.gby.msg.team
1970-01-01 00:00:00.000
grafana.apps.ocp.tc.gby.msg.team
1970-01-01 00:00:00.000
grafana.apps.ocp.test.tc.gby.msg.team
1970-01-01 00:00:00.000
grafana.test.tc.gby.msg.team
1970-01-01 00:00:00.000
grid-dmz.vs-02.msg.team
1970-01-01 00:00:00.000
grid-int.vs-02.msg.team
1970-01-01 00:00:00.000
gw.prod.staffing.m4a.msg.team
1970-01-01 00:00:00.000
gz01.vs-02.msg.team
1970-01-01 00:00:00.000
hamming.yaook.vs-02.msg.team
1970-01-01 00:00:00.000
helaba-dmi.unicorn.stgespl.spl.mgi.msg.team
1970-01-01 00:00:00.000
hub.msg.team
1970-01-01 00:00:00.000
immoscoring.ai-services.mgi.msg.team 2026-06-19 11:17:49.409
intercom.studio.msg.team 2026-06-18 08:36:42.407
iota.msg.team
1970-01-01 00:00:00.000
ipcheck.gbp.msg.team 2026-05-26 05:13:56.978
ipw-test.gbm.msg.team
1970-01-01 00:00:00.000
ipw.gbv.msg.team
1970-01-01 00:00:00.000
it-pisa-spoke02.pisa.msg.team
1970-01-01 00:00:00.000
jaeger.apps.ocp.tc.gby.msg.team 2026-07-18 15:08:57.777
jaeger.apps.ocp.test.tc.gby.msg.team
1970-01-01 00:00:00.000
jaeger.test.tc.gby.msg.team
1970-01-01 00:00:00.000
jenkins.apps.ocp.tc.gby.msg.team
1970-01-01 00:00:00.000
jenkins.apps.ocp.test.tc.gby.msg.team
1970-01-01 00:00:00.000
jenkins.test.tc.gby.msg.team
1970-01-01 00:00:00.000
jira-bvadaisy.publicsector.msg.team
1970-01-01 00:00:00.000
jira.publicsector.msg.team
1970-01-01 00:00:00.000
jitsi.studio.msg.team 2026-07-23 10:40:09.175
k8s-dev.zt.msg.team
1970-01-01 00:00:00.000
kanban-push-test.publicsector.msg.team
1970-01-01 00:00:00.000
kanban-push.publicsector.msg.team 2026-07-22 16:20:18.909
kanban.publicsector.msg.team
1970-01-01 00:00:00.000
kanbanflow.publicsector.msg.team
1970-01-01 00:00:00.000
keycloak.demo.hds.msg.team 2026-06-19 12:30:31.978
keycloak.mds.pisa.msn.msg.team
1970-01-01 00:00:00.000
keycloak.pisa.msn.msg.team
1970-01-01 00:00:00.000
keycloak.pisax.pisa.msn.msg.team
1970-01-01 00:00:00.000
ks3-feature-rk-7964.unicorn.stgespl.spl.mgi.msg.team
1970-01-01 00:00:00.000
lb.prod.staffing.m4a.msg.team
1970-01-01 00:00:00.000
ldaps.vs-02.msg.team
1970-01-01 00:00:00.000
lfa-safe-space-gpt.ai-services.mgi.msg.team
1970-01-01 00:00:00.000
live.studio.msg.team 2026-06-18 08:36:42.407

Tech Stack

Tech detection pending

Wappalyzer-rules detect CMS, frameworks, analytics, JS libs and server-side languages on this domain.

TLS Certificates

Subject: jitsi.studio.msg.team
Issuer: E7
SANs: jitsi.studio.msg.team
Subject: *.msgapi.msg.teams.core.dev.microsoft
Issuer: Non Production Issuing Certificate Authority 2024
SANs: *.msgapi.msg.teams.core.dev.microsoft
Subject: *.ai-services.mgi.msg.team
Issuer: Amazon RSA 2048 M01
SANs: *.ai-services.mgi.msg.team, ai-services.mgi.msg.team
Subject: api.demo.rokr.msgro.msg.team
Issuer: Amazon RSA 2048 M01
SANs: api.demo.rokr.msgro.msg.team
Subject: *.immoscoring.ai-services.mgi.msg.team
Issuer: Amazon RSA 2048 M04
SANs: *.immoscoring.ai-services.mgi.msg.team
Subject: tendermanager.xai.msg.team
Issuer: Amazon RSA 2048 M04
SANs: *.tendermanager.xai.msg.team, tendermanager.xai.msg.team
Subject: fintract-uat.mgi.msg.team
Issuer: Amazon RSA 2048 M01
SANs: *.fintract-uat.mgi.msg.team, fintract-uat.mgi.msg.team
Subject: genai-dev.mgi.msg.team
Issuer: Amazon RSA 2048 M01
SANs: *.genai-dev.mgi.msg.team, genai-dev.mgi.msg.team
Subject: pisa.msn.msg.team
Issuer: Amazon RSA 2048 M01
SANs: *.pisa.msn.msg.team, pisa.msn.msg.team
Subject: genai-uat.mgi.msg.team
Issuer: Amazon RSA 2048 M01
SANs: *.genai-uat.mgi.msg.team, genai-uat.mgi.msg.team
Subject: dev2.pisa.msn.msg.team
Issuer: Amazon RSA 2048 M04
SANs: *.dev2.pisa.msn.msg.team, dev2.pisa.msn.msg.team
Subject: ps.mgi.msg.team
Issuer: Amazon RSA 2048 M02
SANs: *.ps.mgi.msg.team, ps.mgi.msg.team
Subject: genai-dev.mgi.msg.team
Issuer: Amazon RSA 2048 M01
SANs: *.genai-dev.mgi.msg.team, genai-dev.mgi.msg.team
Subject: *.ai-services.mgi.msg.team
Issuer: Amazon RSA 2048 M01
SANs: *.ai-services.mgi.msg.team, ai-services.mgi.msg.team
Subject: marz-pub.mgi.msg.team
Issuer: R13
SANs: *.marz-pub.mgi.msg.team, marz-pub.mgi.msg.team
Subject: *.awsdev.msg.team
Issuer: Amazon ECDSA 256 M04
SANs: *.awsdev.msg.team
Subject: api.staging.rokr.msgro.msg.team
Issuer: Amazon RSA 2048 M04
SANs: api.staging.rokr.msgro.msg.team
Subject: *.ai-services.mgi.msg.team
Issuer: Amazon RSA 2048 M01
SANs: *.ai-services.mgi.msg.team, ai-services.mgi.msg.team
Subject: marz-pub.mgi.msg.team
Issuer: R13
SANs: *.marz-pub.mgi.msg.team, marz-pub.mgi.msg.team
Subject: genai-uat.mgi.msg.team
Issuer: Amazon RSA 2048 M01
SANs: *.genai-uat.mgi.msg.team, genai-uat.mgi.msg.team
Subject: api.test.rokr.msgro.msg.team
Issuer: Amazon RSA 2048 M04
SANs: api.test.rokr.msgro.msg.team
Subject: document-tool.mgi.msg.team
Issuer: Amazon RSA 2048 M01
SANs: *.document-tool.mgi.msg.team, document-tool.mgi.msg.team
Subject: ipcheck.gbp.msg.team
Issuer: R12
SANs: ipcheck.gbp.msg.team
Subject: pisa.msn.msg.team
Issuer: Amazon RSA 2048 M01
SANs: *.pisa.msn.msg.team, pisa.msn.msg.team
Subject: document-tool.mgi.msg.team
Issuer: Amazon RSA 2048 M01
SANs: *.document-tool.mgi.msg.team, document-tool.mgi.msg.team
Subject: ai-services.mgi.msg.team
Issuer: Amazon RSA 2048 M01
SANs: *.ai-services.mgi.msg.team, ai-services.mgi.msg.team

IPs Citing This Domain

No citing IPs found yet

As the world-sweep progresses, hosts referencing this domain in their HTML will surface here.

Origin / IP-Leak

USP

When a hostname is served behind a CDN (e.g. Cloudflare), the origin server can sometimes be identified by matching its TLS cert against the protected hostname. Findings shown here are heuristic candidates, not guarantees.

No origin-IP leaks detected (yet)

Either this domain doesn't sit behind a CDN, or we haven't seen a TLS cert from a non-CDN IP matching this hostname. Run a fullscan to refresh the cert→IP cross-reference.

Threat Intelligence

Domain threat-intel pending

Matches in URLhaus, OpenPhish, PhishTank, malware feeds, and Spamhaus DBL.

History

Domain timeline pending

Passive-DNS history accumulates as our forward-DNS crawler observes A/AAAA/MX/NS/TXT records over time.