postman.com
postman.com describes itself as "Go faster from development to production with higher accuracy and fewer tokens.". It is built on Next.js, registered in 1995, served from Toronto, Canada. It has a valid HTTPS certificate, 4 of 6 common security headers, 2 tracking scripts.
What is postman.com about?
The words appearing most often on the homepage, excluding common filler, are a rough indication of subject matter rather than a description of the business:
- postman ×9
- agents ×8
- apis ×8
- context ×6
- install ×5
- explore ×5
- agent ×4
- every ×4
- graph ×4
- services ×4
Does postman.com publish the usual trust pages?
All four of the pages a established business normally publishes were found: about, contact, privacy and terms. These were checked at conventional paths only, so a site using different URLs may publish them elsewhere.
How does postman.com compare with other domains analysed here?
Measured against the 121 domains in this index. This is a small, self-selected sample — the domains people happened to look up — not a representative sample of the web.
| Response time | Faster than 69% of them (median 790ms) |
|---|---|
| Security headers | More than 93% of them |
| Domain age | Older than 97% of them |
Related domains in this index
Analysed domains sharing the same network (AS13335 Cloudflare, Inc.):
- cloudflare.com
- stackoverflow.com
- npmjs.com
- digitalocean.com
- w3.org
- quikconsole.com
- bettingages.com
- cookiesforlove.com
Sharing a network means sharing a host or CDN. It implies nothing about a relationship between the sites themselves.
Analysed domains built on a similar stack:
Other analysed domains served from the same country:
- netlify.com
- banneradsites.com
- realestatefather.com
- cookape.com.in
- cruzdid.com
- techaudi.com
- calculatewhatever.com
- intointent.com
When was postman.com registered?
postman.com was registered on 13 March 1995, which makes it about 31 years old.
A registration this old means the domain has been renewed repeatedly, which costs money every year and is not something abandoned or disposable projects tend to do.
The registrar of record is Amazon Registrar, Inc..
Registration runs until 14 March 2027.
The domain carries 1 registry lock, which blocks unauthorised transfer or deletion.
| Registered | 13 March 1995 |
|---|---|
| Expires | 14 March 2027 |
| Registrar | Amazon Registrar, Inc. |
| Registry status | client transfer prohibited |
Where is postman.com hosted?
The first address resolves to infrastructure in Toronto, Canada.
The network is operated by Cloudflare, Inc. (AS13335 Cloudflare, Inc.).
Hosting location describes where the responding server sits, not where the business is. A CDN will report its nearest edge rather than the origin.
What is postman.com running on?
postman.com exposes 2 identifiable technologies: Next.js, Cloudflare.
The build output indicates a server-rendered JavaScript framework, which means the HTML served to crawlers is generated ahead of time rather than assembled in the browser.
Cloudflare sits in front of the origin, so the server header, IP addresses and response timing describe the edge rather than the machine actually running the site.
- Next.js
- Cloudflare
How does the homepage respond?
The server answered with HTTP 200 over HTTPS.
At 550ms to first byte this response is unremarkable for a homepage measured from a single European location.
The HTML weighs 490KB, which is ordinary for a homepage.
The HTML is compressed with gzip.
| Server header | cloudflare |
|---|---|
| Compression | gzip |
| Page size | 501,428 bytes |
| Declared language | en |
| Mobile viewport | declared |
What does the homepage say about itself?
The title is 31 characters, inside the range that displays without truncation.
A meta description of 79 characters is present.
All 90 images on the homepage have alt attributes.
| Title | API engineering for your agents (31 chars) |
|---|---|
| Meta description | Go faster from development to production with higher accuracy and fewer tokens. (79 chars) |
| H1 | API engineeringskillscontextsimulationssecurityengineering_engineeringfor your agents (1 on the page) |
| Canonical | https://www.postman.com/ |
| Open Graph title | API engineering for your agents |
| Headings / images | 10 H2s, 90 images (0 without alt text) |
Is postman.com served over a valid certificate?
The HTTPS certificate is issued by Let's Encrypt and is valid until 2026-12-23, which is 80 days from the date of this check. It covers 9 hostnames.
- *.cdn.postman.com
- *.explore.postman.com
- *.go.postman.com
- *.gw.postman.com
- *.id.postman.com
- *.mac.postman.com
- *.postman.com
- *.srv.postman.com
- postman.com
The certificate has 80 days left to run.
Let's Encrypt certificates are free and run on 90-day terms, so this site is almost certainly renewing automatically.
Which security headers does it set?
4 of 6 are set (HSTS, X-Content-Type-Options, X-Frame-Options, Referrer-Policy). Absent: Content Security Policy, Permissions-Policy.
With no Content Security Policy, any script that reaches the page — including one injected through a compromised third-party dependency — runs with full access to it.
| Header | Set | Value |
|---|---|---|
| HSTS | yes | max-age=31536000; includeSubDomains; preload |
| Content Security Policy | no | — |
| X-Content-Type-Options | yes | nosniff |
| X-Frame-Options | yes | SAMEORIGIN |
| Referrer-Policy | yes | strict-origin-when-cross-origin |
| Permissions-Policy | no | — |
How is DNS configured for postman.com?
| IP addresses | 162.159.129.53, 2606:4700:7::a29f:8135 |
|---|---|
| Reverse DNS | 162.159.129.53, 2606:4700:7::a29f:8135 |
| Name servers | ns-745.awsdns-29.net, ns-1497.awsdns-59.org, ns-1576.awsdns-05.co.uk, ns-397.awsdns-49.com |
| Mail (MX) | alt3.aspmx.l.google.com (pri 10), alt4.aspmx.l.google.com (pri 10), alt1.aspmx.l.google.com (pri 5), alt2.aspmx.l.google.com (pri 5), aspmx.l.google.com (pri 1) |
| SPF | v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email ~all |
| TXT records | 50 |
postman.com resolves to 2 addresses, which indicates load balancing or a CDN rather than a single origin server.
Mail is handled by 5 exchangers.
An SPF record is published, giving receiving servers a rule for which hosts may send as this domain.
Reverse DNS resolves to 162.159.129.53, 2606:4700:7::a29f:8135, which usually names the hosting provider.
Who runs DNS and mail for postman.com?
DNS is operated by Amazon Route 53 rather than self-hosted name servers.
Mail is handled by Google Workspace.
The domain publishes AAAA records and accepts connections over IPv6.
What else is worth noting about postman.com?
All 1 externally hosted scripts carry subresource integrity hashes, so a compromised CDN could not silently swap them.
What has changed on postman.com?
This domain has been checked 2 times. Only checks where something actually moved are recorded, so each row below is a real change rather than a repeat measurement.
| Checked | HTTP | Response | IP | Headers |
|---|---|---|---|---|
| 4 Oct 2026 | 200 | 550ms | 162.159.129.53 | 4/6 |
| 4 Oct 2026 | 200 | 638ms | 162.159.129.53 | 4/6 |
Changes recorded at the most recent check:
- name servers: ns-1497.awsdns-59.org,ns-1576.awsdns-05.co.uk,ns-397.awsdns-49.com,ns-745.awsdns-29.net → ns-745.awsdns-29.net,ns-1497.awsdns-59.org,ns-1576.awsdns-05.co.uk,ns-397.awsdns-49.com
- mail servers: alt2.aspmx.l.google.com (pri 5),aspmx.l.google.com (pri 1),alt3.aspmx.l.google.com (pri 10) → alt3.aspmx.l.google.com (pri 10),alt4.aspmx.l.google.com (pri 10),alt1.aspmx.l.google.com (pri 5)
Can postman.com be spoofed in email?
DMARC is set to quarantine, so mail failing authentication is sent to spam rather than the inbox.
CAA records restrict certificate issuance to 6 named authorities (issue amazon.com, issue digicert.com, issue letsencrypt.org, issue pki.goog; cansignhttpexchanges=yes), so no other CA should be able to issue for this domain.
The zone is not DNSSEC-signed. That is still the norm for most domains, but it means DNS answers cannot be cryptographically verified.
What else does postman.com publish?
A security.txt file is published, giving security researchers a documented way to report vulnerabilities. Very few sites bother.
What does robots.txt allow?
robots.txt is 3,118 bytes and names 67 user-agent groups. It does not blanket-disallow general crawlers.
Sitemaps declared:
- https://www.postman.com/sitemap.xml
AI crawler policy
| Crawler | Policy |
|---|---|
| gptbot | allowed |
| claudebot | allowed |
| perplexitybot | allowed |
| google-extended | allowed |
| ccbot | allowed |
| applebot-extended | allowed |
| bytespider | allowed |
| anthropic-ai | allowed |
1 sitemap is declared in robots.txt, which gives crawlers a direct list of URLs.
Named AI crawlers are explicitly allowed (gptbot, claudebot, perplexitybot, google-extended, ccbot, applebot-extended, bytespider, anthropic-ai).
What structured data does the homepage publish?
- Organization
- ContactPoint
- PostalAddress
- Person
- ItemList
- SiteNavigationElement
The homepage publishes 6 structured data types: Organization, ContactPoint, PostalAddress, Person, ItemList, SiteNavigationElement.
What does postman.com load from third parties?
The homepage pulls resources from 10 third-party hosts (connect.facebook.net, facebook.com, googletagmanager.com, js.qualified.com, pages.getpostman.com, px.ads.linkedin.com). Each one sees the visitor IP and user agent on every page load.
7 cookies are set before any interaction (AWSALBTG, AWSALBTGCORS, viewer-country, _pm.uid, _pm.store). 2 lack the Secure flag.
The page links or refers to X/Twitter, LinkedIn, Facebook, Instagram, YouTube, GitHub.
| Cookie | Secure | HttpOnly | SameSite |
|---|---|---|---|
| AWSALBTG | no | no | none/unset |
| AWSALBTGCORS | yes | no | none |
| viewer-country | yes | no | lax |
| _pm.uid | yes | yes | lax |
| _pm.store | no | no | none/unset |
| "traceId":"pmMTc5MTEyMjE4NjAzNw | yes | no | lax |
| __cf_bm | yes | yes | none |
Does postman.com settle on one address?
Plain HTTP redirects to HTTPS, so visitors who type the bare address still land on the secure version.
Both postman.com and www.postman.com answer with 200 and neither redirects to the other. Search engines therefore see two complete copies of the site, and link equity is split between them unless a canonical tag resolves it.
How easily can postman.com be crawled?
A sitemap index is served at https://www.postman.com/sitemap.xml listing 26 entries.
The most recent lastmod date is 2026-07-02.
A deliberately invalid URL returns HTTP 200 rather than 404. That is a soft 404: every mistyped or stale link becomes an indexable page, which inflates the site with duplicates.
What tracking does postman.com run?
2 tracking scripts detected: Meta Pixel, LinkedIn Insight.
No consent management platform was detected alongside them. Where GDPR or the ePrivacy Directive applies, analytics and advertising scripts generally need consent before they load.
How does postman.com look when shared?
4 of 5 social preview tags are set. Missing: og:type.
The page declares 3 hreflang alternates (en, ja, x-default), so it targets more than one language or region.
How are images, fonts and scripts handled?
90 images on the homepage, 76 of them lazy-loaded (84%).
Modern image formats are in use (5 WebP/AVIF references).
No srcset attributes are used, so every device is served the same image size regardless of screen.
The page pulls 11 external stylesheets and 31 external scripts, with 29 carrying defer or async.
Responses carry Cloudflare and Amazon CloudFront and edge cache edge headers, so content is served from a CDN rather than straight from the origin.
Is postman.com accessible and current?
The page uses 14 landmark elements and 372 ARIA attributes.
No skip-to-content link was found, which keyboard users rely on to bypass navigation.
Can search engines index postman.com?
Nothing on the homepage prevents indexing: no noindex is set in the robots meta tag or the X-Robots-Tag header.
The homepage carries 175 internal and 37 external links across 16 outside hosts.
Visible text is only 1.6% of the HTML, which indicates the page is assembled in the browser rather than served as content.
How is postman.com delivered?
The HTML is served with Cache-Control: private, no-store, no-cache, max-age=0, must-revalidate.
A web app manifest is declared, so the site is installable as a progressive web app.
The TLS certificate also covers 7 subdomains: cdn.postman.com, explore.postman.com, go.postman.com, gw.postman.com, id.postman.com, mac.postman.com, srv.postman.com.
- cdn.postman.com
- explore.postman.com
- go.postman.com
- gw.postman.com
- id.postman.com
- mac.postman.com
- srv.postman.com
Frequently asked questions
Does postman.com set the usual HTTP security headers?
It sets 4 of 6. The ones not present are: Content Security Policy, Permissions-Policy.
Does postman.com allow AI crawlers?
robots.txt names no AI crawler specifically, so they fall under the wildcard rule, which does not disallow them.
What is postman.com built with?
The homepage exposes these fingerprints: Next.js, Cloudflare. A site behind a CDN or rendered server-side may use more than it reveals.
Where does this data come from?
Every figure was measured by our own server on 4 October 2026: DNS lookups, one HTTPS request to the homepage, a TLS handshake and a request for robots.txt. No third-party SEO API is involved.
Is any of this traffic or authority data?
No. Traffic, authority and ranking figures cannot be measured by inspecting a domain, only modelled. Everything here is a direct observation.
I own postman.com and want this page removed.
Email hello@quikconsolecom.net from an address at the domain and the report will be taken down. It only ever shows what the domain already serves publicly.
Analysed 4 October 2026. Analyse another domain →