AkamaiGHost
tcp/443 tcp/80
Microsoft-IIS 10.0
tcp/443
awselb 2.0
tcp/443
Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd1aad035491a3b826fe90d52a7828489390e322c04b5177285
Public Swagger UI/API detected at path: /swagger/index.html - sample paths: DELETE /api/v1/TestRemoveAll GET /api/TestSplunk/ping GET /api/v1/AccountID GET /api/v1/AllPushNotifications GET /api/v1/AppVersionCheck GET /api/v1/B2CInstance GET /api/v1/Clean GET /api/v1/CustomerAccounts GET /api/v1/DbHealth GET /api/v1/Devices GET /api/v1/EligibleItems GET /api/v1/EquipmentDBA GET /api/v1/FeaturedArticles GET /api/v1/MasksAndDevices GET /api/v1/MySupportTeam GET /api/v1/Notifications GET /api/v1/Notify GET /api/v1/PAPComplianceStatus GET /api/v1/PatientCommPreferences GET /api/v1/PatientIds GET /api/v1/PatientProfile GET /api/v1/SentNotifications GET /api/v1/ShippingAddressReorder GET /api/v1/TestAllPushNotifications GET /api/v1/TestAuthorization GET /api/v1/TestGetAll GET /api/v1/TestGetNew GET /api/v1/TestNoAuthorization GET /api/v1/TestNotify GET /api/v1/UsageDataResmed GET /api/v1/UsageDataRespironics GET /api/v1/ValidateUser GET /api/v1/ValidateUserB2C POST /api/v1/AddContact POST /api/v1/DisconnectDevice POST /api/v1/Order POST /api/v1/PatientDevice POST /api/v1/RecurringOrderAgreement POST /api/v1/ReportAProblem POST /api/v1/RequestAccountDelete POST /api/v1/SendOTP POST /api/v1/SendOTPPhoneCall POST /api/v1/SendOTPSms POST /api/v1/SignTermsAndConditions PUT /api/v1/Contacts PUT /api/v1/InsuranceCoverage PUT /api/v1/NotificationStatus PUT /api/v1/RemoveAllRONotifications PUT /api/v1/ShippingAddress PUT /api/v1/TestResetNotificationStatuses PUT /api/v1/TestResetNotificationStatusesForPatient
Severity: info
Fingerprint: 5733ddf49ff49cd1aad035491a3b826fe90d52a7828489390e322c04d392f223
Public Swagger UI/API detected at path: /swagger/index.html - sample paths: DELETE /api/v1/TestRemoveAll GET /api/TestSplunk/ping GET /api/v1/AccountID GET /api/v1/AllPushNotifications GET /api/v1/AppVersionCheck GET /api/v1/B2CInstance GET /api/v1/Clean GET /api/v1/CustomerAccounts GET /api/v1/Devices GET /api/v1/EligibleItems GET /api/v1/EquipmentDBA GET /api/v1/FeaturedArticles GET /api/v1/MasksAndDevices GET /api/v1/MySupportTeam GET /api/v1/Notifications GET /api/v1/Notify GET /api/v1/PAPComplianceStatus GET /api/v1/PatientCommPreferences GET /api/v1/PatientIds GET /api/v1/PatientProfile GET /api/v1/SentNotifications GET /api/v1/ShippingAddressReorder GET /api/v1/TestAllPushNotifications GET /api/v1/TestAuthorization GET /api/v1/TestGetAll GET /api/v1/TestGetNew GET /api/v1/TestNoAuthorization GET /api/v1/TestNotify GET /api/v1/UsageDataResmed GET /api/v1/UsageDataRespironics GET /api/v1/ValidateUser GET /api/v1/ValidateUserB2C POST /api/v1/AddContact POST /api/v1/DisconnectDevice POST /api/v1/Order POST /api/v1/PatientDevice POST /api/v1/RecurringOrderAgreement POST /api/v1/ReportAProblem POST /api/v1/RequestAccountDelete POST /api/v1/SendOTP POST /api/v1/SendOTPPhoneCall POST /api/v1/SendOTPSms POST /api/v1/SignTermsAndConditions PUT /api/v1/Contacts PUT /api/v1/InsuranceCoverage PUT /api/v1/NotificationStatus PUT /api/v1/RemoveAllRONotifications PUT /api/v1/ShippingAddress PUT /api/v1/TestResetNotificationStatuses PUT /api/v1/TestResetNotificationStatusesForPatient
Severity: info
Fingerprint: 5733ddf49ff49cd1aad035491a3b826ffd58fbc1e2c5212ccc46c24f95205ed0
Public Swagger UI/API detected at path: /swagger/index.html - sample paths: DELETE /api/v1/TestRemoveAll GET /api/v1/AccountID GET /api/v1/AllPushNotifications GET /api/v1/AppVersionCheck GET /api/v1/B2CInstance GET /api/v1/Clean GET /api/v1/CustomerAccounts GET /api/v1/Devices GET /api/v1/EligibleItems GET /api/v1/EquipmentDBA GET /api/v1/FeaturedArticles GET /api/v1/MasksAndDevices GET /api/v1/MySupportTeam GET /api/v1/Notifications GET /api/v1/Notify GET /api/v1/PAPComplianceStatus GET /api/v1/PatientCommPreferences GET /api/v1/PatientIds GET /api/v1/PatientProfile GET /api/v1/SentNotifications GET /api/v1/ShippingAddressReorder GET /api/v1/TestAllPushNotifications GET /api/v1/TestAuthorization GET /api/v1/TestGetAll GET /api/v1/TestGetNew GET /api/v1/TestNoAuthorization GET /api/v1/TestNotify GET /api/v1/UsageDataResmed GET /api/v1/UsageDataRespironics GET /api/v1/ValidateUser GET /api/v1/ValidateUserB2C GET /api/v1/core-ping GET /api/v1/debug/token POST /api/v1/AddContact POST /api/v1/DisconnectDevice POST /api/v1/Order POST /api/v1/PatientDevice POST /api/v1/RecurringOrderAgreement POST /api/v1/ReportAProblem POST /api/v1/RequestAccountDelete POST /api/v1/SendOTP POST /api/v1/SendOTPPhoneCall POST /api/v1/SendOTPSms POST /api/v1/SignTermsAndConditions PUT /api/v1/Contacts PUT /api/v1/InsuranceCoverage PUT /api/v1/NotificationStatus PUT /api/v1/RemoveAllRONotifications PUT /api/v1/ShippingAddress PUT /api/v1/TestResetNotificationStatuses PUT /api/v1/TestResetNotificationStatusesForPatient
Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd1aad03549115947422cebc70c8317dd1ba833674224b0b168
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
GET /api/v1/DobAllowed
GET /api/v1/GoogleApiKey
GET /api/v1/Logs
GET /api/v1/Message
GET /api/v1/ResendSmsInfo
POST /api/v1/DeliveryTimes
POST /api/v1/DobZip
POST /api/v1/Log
POST /api/v1/NewShippingAddress
POST /api/v1/OneTimeLink/{urlParam}
POST /api/v1/Order
POST /api/v1/PhoneNumber
POST /api/v1/PhoneNumberQr
POST /api/v1/SendEmailToForeignBranches
Severity: info
Fingerprint: 5733ddf49ff49cd1f3d88d6012d166df3ac6754165b3d84243ec20255fc481f9
Public Swagger UI/API detected at path: /swagger/v1/swagger.json - sample paths:
GET /api/v1/DobAllowed
GET /api/v1/GoogleApiKey
GET /api/v1/Logs
GET /api/v1/Message
GET /api/v1/ResendSmsInfo
POST /api/v1/DeliveryTimes
POST /api/v1/DobZip
POST /api/v1/Log
POST /api/v1/NewShippingAddress
POST /api/v1/OneTimeLink/{urlParam}
POST /api/v1/Order
POST /api/v1/PhoneNumber
POST /api/v1/PhoneNumberQr
POST /api/v1/SendEmailToForeignBranches
Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd1aad035491a3b826ffd58fbc1e2c5212ccc46c24fd8e73494
Public Swagger UI/API detected at path: /swagger/index.html - sample paths: DELETE /api/v1/TestRemoveAll GET /api/v1/AccountID GET /api/v1/AllPushNotifications GET /api/v1/AppVersionCheck GET /api/v1/B2CInstance GET /api/v1/Clean GET /api/v1/CustomerAccounts GET /api/v1/DbHealth GET /api/v1/Devices GET /api/v1/EligibleItems GET /api/v1/EquipmentDBA GET /api/v1/FeaturedArticles GET /api/v1/FeedbackRequestForm GET /api/v1/MySupportTeam GET /api/v1/Notifications GET /api/v1/Notify GET /api/v1/PAPComplianceStatus GET /api/v1/PatientCommPreferences GET /api/v1/PatientIds GET /api/v1/PatientProfile GET /api/v1/SentNotifications GET /api/v1/ShippingAddressReorder GET /api/v1/TestAllPushNotifications GET /api/v1/TestAuthorization GET /api/v1/TestGetAll GET /api/v1/TestGetNew GET /api/v1/TestNoAuthorization GET /api/v1/TestNotify GET /api/v1/UsageDataResmed GET /api/v1/UsageDataRespironics GET /api/v1/ValidateUser GET /api/v1/ValidateUserB2C GET /api/v1/core-ping GET /api/v1/debug/token POST /api/v1/AddContact POST /api/v1/DisconnectDevice POST /api/v1/FeedbackRequestFormResponse POST /api/v1/Order POST /api/v1/PatientDevice POST /api/v1/RecurringOrderAgreement POST /api/v1/ReportAProblem POST /api/v1/RequestAccountDelete POST /api/v1/SendOTP POST /api/v1/SendOTPPhoneCall POST /api/v1/SendOTPSms POST /api/v1/SignTermsAndConditions PUT /api/v1/Contacts PUT /api/v1/InsuranceCoverage PUT /api/v1/NotificationStatus PUT /api/v1/RemoveAllRONotifications PUT /api/v1/ShippingAddress PUT /api/v1/TestResetNotificationStatuses PUT /api/v1/TestResetNotificationStatusesForPatient
Severity: info
Fingerprint: 5733ddf49ff49cd1aad035491a3b826ffd58fbc1e2c5212ccc46c24fca248c8b
Public Swagger UI/API detected at path: /swagger/index.html - sample paths: DELETE /api/v1/TestRemoveAll GET /api/v1/AccountID GET /api/v1/AllPushNotifications GET /api/v1/AppVersionCheck GET /api/v1/B2CInstance GET /api/v1/Clean GET /api/v1/CustomerAccounts GET /api/v1/DbHealth GET /api/v1/Devices GET /api/v1/EligibleItems GET /api/v1/EquipmentDBA GET /api/v1/FeaturedArticles GET /api/v1/FeedbackRequestForm GET /api/v1/MySupportTeam GET /api/v1/Notifications GET /api/v1/Notify GET /api/v1/PAPComplianceStatus GET /api/v1/PatientCommPreferences GET /api/v1/PatientIds GET /api/v1/PatientProfile GET /api/v1/SentNotifications GET /api/v1/ShippingAddressReorder GET /api/v1/TestAllPushNotifications GET /api/v1/TestAuthorization GET /api/v1/TestGetAll GET /api/v1/TestGetNew GET /api/v1/TestNoAuthorization GET /api/v1/TestNotify GET /api/v1/UsageDataResmed GET /api/v1/UsageDataRespironics GET /api/v1/ValidateUser GET /api/v1/ValidateUserB2C GET /api/v1/core-ping GET /api/v1/debug/token POST /FeedbackRequestFormResponse POST /api/v1/AddContact POST /api/v1/DisconnectDevice POST /api/v1/Order POST /api/v1/PatientDevice POST /api/v1/RecurringOrderAgreement POST /api/v1/ReportAProblem POST /api/v1/RequestAccountDelete POST /api/v1/SendOTP POST /api/v1/SendOTPPhoneCall POST /api/v1/SendOTPSms POST /api/v1/SignTermsAndConditions PUT /api/v1/Contacts PUT /api/v1/InsuranceCoverage PUT /api/v1/NotificationStatus PUT /api/v1/RemoveAllRONotifications PUT /api/v1/ShippingAddress PUT /api/v1/TestResetNotificationStatuses PUT /api/v1/TestResetNotificationStatusesForPatient
Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd1aad035491a3b826fe90d52a7828489390e322c04d392f223
Public Swagger UI/API detected at path: /swagger/index.html - sample paths: DELETE /api/v1/TestRemoveAll GET /api/TestSplunk/ping GET /api/v1/AccountID GET /api/v1/AllPushNotifications GET /api/v1/AppVersionCheck GET /api/v1/B2CInstance GET /api/v1/Clean GET /api/v1/CustomerAccounts GET /api/v1/Devices GET /api/v1/EligibleItems GET /api/v1/EquipmentDBA GET /api/v1/FeaturedArticles GET /api/v1/MasksAndDevices GET /api/v1/MySupportTeam GET /api/v1/Notifications GET /api/v1/Notify GET /api/v1/PAPComplianceStatus GET /api/v1/PatientCommPreferences GET /api/v1/PatientIds GET /api/v1/PatientProfile GET /api/v1/SentNotifications GET /api/v1/ShippingAddressReorder GET /api/v1/TestAllPushNotifications GET /api/v1/TestAuthorization GET /api/v1/TestGetAll GET /api/v1/TestGetNew GET /api/v1/TestNoAuthorization GET /api/v1/TestNotify GET /api/v1/UsageDataResmed GET /api/v1/UsageDataRespironics GET /api/v1/ValidateUser GET /api/v1/ValidateUserB2C POST /api/v1/AddContact POST /api/v1/DisconnectDevice POST /api/v1/Order POST /api/v1/PatientDevice POST /api/v1/RecurringOrderAgreement POST /api/v1/ReportAProblem POST /api/v1/RequestAccountDelete POST /api/v1/SendOTP POST /api/v1/SendOTPPhoneCall POST /api/v1/SendOTPSms POST /api/v1/SignTermsAndConditions PUT /api/v1/Contacts PUT /api/v1/InsuranceCoverage PUT /api/v1/NotificationStatus PUT /api/v1/RemoveAllRONotifications PUT /api/v1/ShippingAddress PUT /api/v1/TestResetNotificationStatuses PUT /api/v1/TestResetNotificationStatusesForPatient
Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd1aad035491a3b826fe90d52a7828489390e322c04d392f223
Public Swagger UI/API detected at path: /swagger/index.html - sample paths: DELETE /api/v1/TestRemoveAll GET /api/TestSplunk/ping GET /api/v1/AccountID GET /api/v1/AllPushNotifications GET /api/v1/AppVersionCheck GET /api/v1/B2CInstance GET /api/v1/Clean GET /api/v1/CustomerAccounts GET /api/v1/Devices GET /api/v1/EligibleItems GET /api/v1/EquipmentDBA GET /api/v1/FeaturedArticles GET /api/v1/MasksAndDevices GET /api/v1/MySupportTeam GET /api/v1/Notifications GET /api/v1/Notify GET /api/v1/PAPComplianceStatus GET /api/v1/PatientCommPreferences GET /api/v1/PatientIds GET /api/v1/PatientProfile GET /api/v1/SentNotifications GET /api/v1/ShippingAddressReorder GET /api/v1/TestAllPushNotifications GET /api/v1/TestAuthorization GET /api/v1/TestGetAll GET /api/v1/TestGetNew GET /api/v1/TestNoAuthorization GET /api/v1/TestNotify GET /api/v1/UsageDataResmed GET /api/v1/UsageDataRespironics GET /api/v1/ValidateUser GET /api/v1/ValidateUserB2C POST /api/v1/AddContact POST /api/v1/DisconnectDevice POST /api/v1/Order POST /api/v1/PatientDevice POST /api/v1/RecurringOrderAgreement POST /api/v1/ReportAProblem POST /api/v1/RequestAccountDelete POST /api/v1/SendOTP POST /api/v1/SendOTPPhoneCall POST /api/v1/SendOTPSms POST /api/v1/SignTermsAndConditions PUT /api/v1/Contacts PUT /api/v1/InsuranceCoverage PUT /api/v1/NotificationStatus PUT /api/v1/RemoveAllRONotifications PUT /api/v1/ShippingAddress PUT /api/v1/TestResetNotificationStatuses PUT /api/v1/TestResetNotificationStatusesForPatient
Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd1aad035491a3b826fe90d52a7828489390e322c04d392f223
Public Swagger UI/API detected at path: /swagger/index.html - sample paths: DELETE /api/v1/TestRemoveAll GET /api/TestSplunk/ping GET /api/v1/AccountID GET /api/v1/AllPushNotifications GET /api/v1/AppVersionCheck GET /api/v1/B2CInstance GET /api/v1/Clean GET /api/v1/CustomerAccounts GET /api/v1/Devices GET /api/v1/EligibleItems GET /api/v1/EquipmentDBA GET /api/v1/FeaturedArticles GET /api/v1/MasksAndDevices GET /api/v1/MySupportTeam GET /api/v1/Notifications GET /api/v1/Notify GET /api/v1/PAPComplianceStatus GET /api/v1/PatientCommPreferences GET /api/v1/PatientIds GET /api/v1/PatientProfile GET /api/v1/SentNotifications GET /api/v1/ShippingAddressReorder GET /api/v1/TestAllPushNotifications GET /api/v1/TestAuthorization GET /api/v1/TestGetAll GET /api/v1/TestGetNew GET /api/v1/TestNoAuthorization GET /api/v1/TestNotify GET /api/v1/UsageDataResmed GET /api/v1/UsageDataRespironics GET /api/v1/ValidateUser GET /api/v1/ValidateUserB2C POST /api/v1/AddContact POST /api/v1/DisconnectDevice POST /api/v1/Order POST /api/v1/PatientDevice POST /api/v1/RecurringOrderAgreement POST /api/v1/ReportAProblem POST /api/v1/RequestAccountDelete POST /api/v1/SendOTP POST /api/v1/SendOTPPhoneCall POST /api/v1/SendOTPSms POST /api/v1/SignTermsAndConditions PUT /api/v1/Contacts PUT /api/v1/InsuranceCoverage PUT /api/v1/NotificationStatus PUT /api/v1/RemoveAllRONotifications PUT /api/v1/ShippingAddress PUT /api/v1/TestResetNotificationStatuses PUT /api/v1/TestResetNotificationStatusesForPatient
Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd1aad035491a3b826ffd58fbc1e2c5212ccc46c24f11e64294
Public Swagger UI/API detected at path: /swagger/index.html - sample paths: DELETE /api/v1/TestRemoveAll GET /api/v1/AccountID GET /api/v1/AllPushNotifications GET /api/v1/AppVersionCheck GET /api/v1/B2CInstance GET /api/v1/Clean GET /api/v1/CustomerAccounts GET /api/v1/Devices GET /api/v1/EligibleItems GET /api/v1/EquipmentDBA GET /api/v1/FeaturedArticles GET /api/v1/MySupportTeam GET /api/v1/Notifications GET /api/v1/Notify GET /api/v1/PAPComplianceStatus GET /api/v1/PatientCommPreferences GET /api/v1/PatientIds GET /api/v1/PatientProfile GET /api/v1/SentNotifications GET /api/v1/ShippingAddressReorder GET /api/v1/TestAllPushNotifications GET /api/v1/TestAuthorization GET /api/v1/TestGetAll GET /api/v1/TestGetNew GET /api/v1/TestNoAuthorization GET /api/v1/TestNotify GET /api/v1/UsageDataResmed GET /api/v1/UsageDataRespironics GET /api/v1/ValidateUser GET /api/v1/ValidateUserB2C POST /api/v1/AddContact POST /api/v1/DisconnectDevice POST /api/v1/Order POST /api/v1/PatientDevice POST /api/v1/RecurringOrderAgreement POST /api/v1/ReportAProblem POST /api/v1/RequestAccountDelete POST /api/v1/SendOTP POST /api/v1/SendOTPPhoneCall POST /api/v1/SendOTPSms POST /api/v1/SignTermsAndConditions PUT /api/v1/Contacts PUT /api/v1/InsuranceCoverage PUT /api/v1/NotificationStatus PUT /api/v1/RemoveAllRONotifications PUT /api/v1/ShippingAddress PUT /api/v1/TestResetNotificationStatuses PUT /api/v1/TestResetNotificationStatusesForPatient
Open service 104.110.240.89:443 · text2order-api.lincare.com
2026-01-27 10:52
HTTP/1.1 404 Not Found Content-Length: 0 Server: Microsoft-IIS/10.0 X-Powered-By: ASP.NET Date: Tue, 27 Jan 2026 10:52:56 GMT Connection: close Set-Cookie: ARRAffinity=b3fc68825d4c0187e5068d5b13b911a47383c023416d45b3a77817aab84fb695;Path=/;HttpOnly;Secure;Domain=app-o2o-smso2ordering-api-prod-eastus2-001.azurewebsites.net Set-Cookie: ARRAffinitySameSite=b3fc68825d4c0187e5068d5b13b911a47383c023416d45b3a77817aab84fb695;Path=/;HttpOnly;SameSite=None;Secure;Domain=app-o2o-smso2ordering-api-prod-eastus2-001.azurewebsites.net
Open service 2.16.204.77:443 · dev.vent.lincare.com
2026-01-23 09:09
HTTP/1.1 404 Not Found Content-Length: 0 Server: Microsoft-IIS/10.0 Request-Context: appId=cid-v1:07c53777-23f2-49f5-aea3-0a8dd590e195 X-Powered-By: ASP.NET Date: Fri, 23 Jan 2026 09:09:21 GMT Connection: close Set-Cookie: ARRAffinity=55d91db73d129abae001285ffaf738293331678d728f2dc14d2c3dd500b74697;Path=/;HttpOnly;Secure;Domain=app-ventapp-devb-eastus2-001.azurewebsites.net Set-Cookie: ARRAffinitySameSite=55d91db73d129abae001285ffaf738293331678d728f2dc14d2c3dd500b74697;Path=/;HttpOnly;SameSite=None;Secure;Domain=app-ventapp-devb-eastus2-001.azurewebsites.net
Open service 23.36.162.219:443 · lincare.com
2026-01-21 16:32
HTTP/1.1 301 Moved Permanently Server: AkamaiGHost Content-Length: 0 Location: https://www.lincare.com Date: Wed, 21 Jan 2026 16:32:43 GMT Connection: close
Open service 2a02:26f0:3500:18::1724:a29a:80 · lincare.com
2026-01-21 16:32
HTTP/1.1 301 Moved Permanently Server: AkamaiGHost Content-Length: 0 Location: https://www.lincare.com Date: Wed, 21 Jan 2026 16:33:05 GMT Connection: close
Open service 23.36.162.207:80 · lincare.com
2026-01-21 16:32
HTTP/1.1 301 Moved Permanently Server: AkamaiGHost Content-Length: 0 Location: https://www.lincare.com Date: Wed, 21 Jan 2026 16:33:05 GMT Connection: close
Open service 23.36.162.219:80 · lincare.com
2026-01-21 16:32
HTTP/1.1 301 Moved Permanently Server: AkamaiGHost Content-Length: 0 Location: https://www.lincare.com Date: Wed, 21 Jan 2026 16:33:05 GMT Connection: close
Open service 2a02:26f0:3500:18::1724:a29a:443 · lincare.com
2026-01-21 16:32
HTTP/1.1 301 Moved Permanently Server: AkamaiGHost Content-Length: 0 Location: https://www.lincare.com Date: Wed, 21 Jan 2026 16:32:43 GMT Connection: close
Open service 2a02:26f0:3500:18::1724:a298:443 · lincare.com
2026-01-21 16:32
HTTP/1.1 301 Moved Permanently Server: AkamaiGHost Content-Length: 0 Location: https://www.lincare.com Date: Wed, 21 Jan 2026 16:32:43 GMT Connection: close
Open service 2a02:26f0:3500:18::1724:a298:80 · lincare.com
2026-01-21 16:32
HTTP/1.1 301 Moved Permanently Server: AkamaiGHost Content-Length: 0 Location: https://www.lincare.com Date: Wed, 21 Jan 2026 16:33:02 GMT Connection: close
Open service 23.36.162.207:443 · lincare.com
2026-01-21 16:32
HTTP/1.1 301 Moved Permanently Server: AkamaiGHost Content-Length: 0 Location: https://www.lincare.com Date: Wed, 21 Jan 2026 16:32:43 GMT Connection: close
Open service 54.82.45.218:443 · order.lincare.com
2026-01-09 15:20
HTTP/1.1 403 Forbidden Server: awselb/2.0 Date: Fri, 09 Jan 2026 15:20:39 GMT Content-Type: text/html Content-Length: 118 Connection: close Page title: 403 Forbidden <html> <head><title>403 Forbidden</title></head> <body> <center><h1>403 Forbidden</h1></center> </body> </html>
Open service 34.194.49.35:443 · order.lincare.com
2026-01-09 15:20
HTTP/1.1 403 Forbidden Server: awselb/2.0 Date: Fri, 09 Jan 2026 15:20:38 GMT Content-Type: text/html Content-Length: 118 Connection: close Page title: 403 Forbidden <html> <head><title>403 Forbidden</title></head> <body> <center><h1>403 Forbidden</h1></center> </body> </html>
Open service 54.209.14.197:443 · order.lincare.com
2026-01-09 15:20
HTTP/1.1 403 Forbidden Server: awselb/2.0 Date: Fri, 09 Jan 2026 15:20:38 GMT Content-Type: text/html Content-Length: 118 Connection: close Page title: 403 Forbidden <html> <head><title>403 Forbidden</title></head> <body> <center><h1>403 Forbidden</h1></center> </body> </html>